CVE-2018-25042 json
uTorrent memory corruption
published 4y ago modified 4mo ago also EUVD-2018-13814
- cvss
- 5.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
A vulnerability classified as critical has been found in uTorrent. This affects an unknown part. The manipulation leads to memory corruption. It is possible to initiate the attack remotely. It is recommended to upgrade the affected component.
Is CVE-2018-25042 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
1.02% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- bugs.chromium.org https://bugs.chromium.org/p/project-zero/issues/detail?id=1524 referenced PoC, tagged "exploit" by a source, unverified
- vuldb.com https://vuldb.com/?id.113805 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- unspecified uTorrent
Classification
References
-
bugs.chromium.org
/p/project-zero/issues/detail?id=1524
exploit, issue-tracking, mailing-list, third-party-advisory
-
vuldb.com
/?id.113805
exploit, third-party-advisory, vdb-entry
-
scmagazineuk.com
/utorrent-apps-vulnerable-to-remote-code-execution-information-disclosure/article/746248/
not-applicable
Sources
- CVE List CVE-2018-25042
- NVD CVE-2018-25042
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.