CVE-2017-11785 json
The Microsoft Windows Kernel component on Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gol…
published 2017-10-13 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-3393
- cvss
- 5.5
- version 3.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 Microsoft Windows Kernel component on Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016, allows an information disclosure vulnerability when it improperly handles objects in memory, aka "Windows Kernel Information Disclosure Vulnerability". This CVE ID is unique from CVE-2017-11765, CVE-2017-11784, and CVE-2017-11814.
Patch / fix
Timeline
- Published
- First public exploit (EDB-43001)
Exploit prediction
3.02% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-43001 Microsoft Windows - 'nt!NtQueryObject (ObjectNameInformation)' Kernel Pool Memory Disclosure dos, 2017-10-17
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.5 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- Microsoft Corporation Windows Kernel
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2017-11785
patch, vendor-advisory
-
exploit-db.com
/exploits/43001/
exploit, third-party-advisory, vdb-entry
-
securitytracker.com
/id/1039526
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/101149
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-11785
- NVD CVE-2017-11785
Fencer Vulns 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.