CVE-2017-0038
What it is
gdi32.dll in Graphics Device Interface (GDI) in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, and Windows 10 Gold, 1511, and 1607 allows remote attackers to obtain sensitive information from process heap memory via a crafted EMF file, as demonstrated by an EMR_SETDIBITSTODEVICE record with modified Device Independent Bitmap (DIB) dimensions. NOTE: this vulnerability exists because of an incomplete fix for CVE-2016-3216, CVE-2016-3219, and/or CVE-2016-3220.
At a glance
- Exploitability
- Can be exploited locally on the machine without logging in, but needs a user to act. High risk of data exposure.
- Exploit odds
- 82.2% chance of exploitation in the next 30 days (EPSS). Higher than most.
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 82.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 82.2% · EPSS, next 30 days
- Weakness
- CWE-200 · Information exposure
- Record status
- Modified
Affected
- Microsoft Windows 10
- Microsoft Windows 10 1511
- Microsoft Windows 10 1607
- Microsoft Windows 7
- Microsoft Windows 8.1
- Microsoft Windows Rt 8.1
- Microsoft Windows Server 2008
- Microsoft Windows Server 2008 r2
Attack profile CVSS 3.0 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Raw vector
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2017-0038.md and follow it. Check whether this project is affected by CVE-2017-0038. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://0patch.blogspot.com/2017/02/0patching-0-day-windows-gdi32dll-memory.html
- https://bugs.chromium.org/p/project-zero/issues/detail?id=992
- https://0patch.blogspot.com/2017/02/0patching-0-day-windows-gdi32dll-memory.html
- https://bugs.chromium.org/p/project-zero/issues/detail?id=992
References
- http://www.securityfocus.com/bid/96023
- http://www.securitytracker.com/id/1037845
- https://0patch.blogspot.com/2017/02/0patching-0-day-windows-gdi32dll-memory.html
- https://bugs.chromium.org/p/project-zero/issues/detail?id=992
- https://github.com/k0keoyo/CVE-2017-0038-EXP-C-JS
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-0038
- https://www.exploit-db.com/exploits/41363/
- http://www.securityfocus.com/bid/96023
- http://www.securitytracker.com/id/1037845
- https://0patch.blogspot.com/2017/02/0patching-0-day-windows-gdi32dll-memory.html
- https://bugs.chromium.org/p/project-zero/issues/detail?id=992
- https://github.com/k0keoyo/CVE-2017-0038-EXP-C-JS
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-0038
- https://www.exploit-db.com/exploits/41363/