CVE-2018-25043 json
uTorrent PRNG improper authentication
published 4y ago modified 4mo ago also EUVD-2018-13815
- cvss
- 5.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
A vulnerability classified as critical was found in uTorrent. This vulnerability affects unknown code of the component PRNG. The manipulation leads to weak authentication. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. It is recommended to upgrade the affected component.
Is CVE-2018-25043 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.18% chance of exploitation in the next 30 days, higher than 67% 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.113806 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
- Weakness
-
- CWE-287 Improper Authentication
References
-
bugs.chromium.org
/p/project-zero/issues/detail?id=1524
exploit, issue-tracking, mailing-list, third-party-advisory
-
vuldb.com
/?id.113806
exploit, permissions-required, third-party-advisory, vdb-entry
-
math.sci.hiroshima-u.ac.jp
/~m-mat/MT/efaq.html
third-party-advisory
Sources
- CVE List CVE-2018-25043
- NVD CVE-2018-25043
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.