CVE-2018-25044 json
uTorrent Guest Account privileges management
published 4y ago modified 4mo ago also EUVD-2018-13816
- cvss
- 6.3
- 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 62%
- public exploits
- 0
- none known
Summary
A vulnerability, which was classified as critical, has been found in uTorrent. This issue affects some unknown processing of the component Guest Account. The manipulation leads to privilege escalation. The attack may 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-25044 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
0.99% chance of exploitation in the next 30 days, higher than 62% 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.113807 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.3 | CVSS:3.1/AV:N/AC:L/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-269 Improper Privilege Management
References
-
bugs.chromium.org
/p/project-zero/issues/detail?id=1524
exploit, issue-tracking, mailing-list, third-party-advisory
-
vuldb.com
/?id.113807
exploit, third-party-advisory, vdb-entry
-
math.sci.hiroshima-u.ac.jp
/~m-mat/MT/efaq.html
third-party-advisory
Sources
- CVE List CVE-2018-25044
- NVD CVE-2018-25044
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.