Code execution via crafted image processing
Published Apr 15, 2020 · Updated Aug 4, 2024
Memory corruption in Microsoft Windows Codecs Library allows local users to execute arbitrary code when a program processes a crafted image file. Microsoft has disclosed only that the library mishandles objects in memory and has not identified the faulty routine or operation. Exploitation requires delivery and processing of the crafted image; successful code runs in the security context of the processing program.
Summary
What happened
Memory corruption in Microsoft Windows Codecs Library allows local users to execute arbitrary code when a program processes a crafted image file. Microsoft has disclosed only that the library mishandles objects in memory and has not identified the faulty routine or operation. Exploitation requires delivery and processing of the crafted image; successful code runs in the security context of the processing program.
The record
- CVE
- CVE-2020-0965
- Published
- Apr 15, 2020
- Updated
- Aug 4, 2024
- Vendor
- Microsoft
- Product
- Windows 10 Version 1909
- Classifications
- T1203
- Attack vector
- local
- Privileges
- authenticated
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