Code execution via improper in-memory object handling
Published Apr 15, 2020 · Updated Aug 4, 2024
Memory corruption in Microsoft Graphics Components in affected Windows releases allows attackers to execute code via a crafted file. The component improperly handles objects in memory, but Microsoft has not disclosed the specific object type, processing path, or invalid memory operation. Exploitation requires a local user to open attacker-controlled content, and successful code runs in that user's security context.
Summary
What happened
Memory corruption in Microsoft Graphics Components in affected Windows releases allows attackers to execute code via a crafted file. The component improperly handles objects in memory, but Microsoft has not disclosed the specific object type, processing path, or invalid memory operation. Exploitation requires a local user to open attacker-controlled content, and successful code runs in that user's security context.
The record
- CVE
- CVE-2020-0907
- Published
- Apr 15, 2020
- Updated
- Aug 4, 2024
- Vendor
- Microsoft
- Product
- Windows 10 Version 1909
- Classifications
- T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 15, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo