CVE-2015-6102 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 10y ago modified 4mo ago also EUVD-2015-6045
- cvss
- 2.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.8%
- EPSS 3.8% chance of exploitation in 30 days, percentile 90%
- 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 Gold and 1511 allows local users to bypass the KASLR protection mechanism, and consequently discover a driver base address, via a crafted application, aka "Windows Kernel Memory Information Disclosure Vulnerability."
Patch / fix
Is CVE-2015-6102 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-38794)
Exploit prediction
3.82% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-38794 Microsoft Windows - Cursor Object Memory Leak (MS15-115) dos, 2015-11-23
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2015/ms15-115
vendor-advisory, patch
-
exploit-db.com
/exploits/38794/
exploit, third-party-advisory, vdb-entry
-
securitytracker.com
/id/1034114
vdb-entry, third-party-advisory
-
packetstormsecurity.com
/files/134519/Microsoft-Windows-Cursor-Object-Potential-Memory-Leak.html
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2015-6102
- NVD CVE-2015-6102
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.