CVE-2015-2553 json
The kernel in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 G…
published 11y ago modified 4mo ago also EUVD-2015-2646
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.0%
- EPSS 3.0% chance of exploitation in 30 days, percentile 87%
- public exploits
- 1
- Exploit-DB
Summary
The kernel in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT Gold and 8.1, and Windows 10 mishandles junctions during mountpoint creation, which makes it easier for local users to gain privileges by leveraging certain sandbox access, aka "Windows Mount Point Elevation of Privilege Vulnerability."
Patch / fix
Is CVE-2015-2553 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 FencerTimeline
- Published
- First public exploit (EDB-38474)
Exploit prediction
3.04% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-38474 Microsoft Windows 10 - Sandboxed Mount Reparse Point Creation Mitigation Bypass (MS15-111) local, 2015-10-15
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2015/ms15-111
vendor-advisory, patch
-
exploit-db.com
/exploits/38474/
exploit, third-party-advisory, vdb-entry
-
securitytracker.com
/id/1033805
vdb-entry, third-party-advisory
-
packetstormsecurity.com
/files/133971/Windows-Sandboxed-Mount-Reparse-Point-Creation-Mitigation-Bypass.html
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2015-2553
- NVD CVE-2015-2553
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.