Local privilege escalation
Published Feb 11, 2020 · Updated Aug 4, 2024
Memory corruption in the Microsoft Windows Graphics Component allows local users to run processes with elevated privileges via a crafted application. Microsoft has not published the affected object type, function, or exact memory-safety error beyond improper handling of objects in memory. A low-privileged local account is required, and successful exploitation permits control of the affected system.
Summary
What happened
Memory corruption in the Microsoft Windows Graphics Component allows local users to run processes with elevated privileges via a crafted application. Microsoft has not published the affected object type, function, or exact memory-safety error beyond improper handling of objects in memory. A low-privileged local account is required, and successful exploitation permits control of the affected system.
The record
- CVE
- CVE-2020-0745
- Published
- Feb 11, 2020
- Updated
- Aug 4, 2024
- Vendor
- Microsoft
- Product
- Windows 10 Version 1909
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 11, 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