CVE-2017-8682 in the critical feed json
Windows graphics on Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8…
published 2017-09-13 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-17629
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 49.8%
- EPSS 49.8% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB
Summary
Windows graphics 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, Windows Server 2016, Microsoft Office Word Viewer, Microsoft Office 2007 Service Pack 3 , and Microsoft Office 2010 Service Pack 2 allows an attacker to execute remote code by the way it handles embedded fonts, aka "Win32k Graphics Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-8683.
Patch / fix
Timeline
- Published
- First public exploit (EDB-42744)
Exploit prediction
49.77% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-42744 Microsoft Windows Kernel - 'win32k.sys' '.TTF' Font Processing Out-of-Bounds Reads/Writes with Malformed 'fpgm' table 'win32k!bGeneratePath' (Denial of Service) dos, 2017-09-18
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Affected products
- Microsoft Corporation Windows graphics
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
portal.msrc.microsoft.com
/en-US/security-guidance/advisory/CVE-2017-8682
patch, vendor-advisory
-
exploit-db.com
/exploits/42744/
exploit, third-party-advisory, vdb-entry
-
securitytracker.com
/id/1039352
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/100772
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-8682
- NVD CVE-2017-8682
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.