Code execution via improper object handling
Published May 21, 2020 · Updated Aug 19, 2026
Memory corruption in Windows Media Foundation on Windows 7 and Server 2008 R2 SP1 allows attackers to execute code via crafted content. Microsoft has disclosed only that Media Foundation improperly handles objects in memory; the specific parser and overwrite operation are not public. Exploitation requires a user to open a crafted document or visit a malicious webpage, after which code runs with the user's rights.
Summary
What happened
Memory corruption in Windows Media Foundation on Windows 7 and Server 2008 R2 SP1 allows attackers to execute code via crafted content. Microsoft has disclosed only that Media Foundation improperly handles objects in memory; the specific parser and overwrite operation are not public. Exploitation requires a user to open a crafted document or visit a malicious webpage, after which code runs with the user's rights.
The record
- CVE
- CVE-2020-1150
- Published
- May 21, 2020
- Updated
- Aug 19, 2026
- Vendor
- Microsoft
- Product
- Windows 7
- Classifications
- CWE-787, T1204.002, T1204.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 21, 2020CVE publishedPublication date reported by the CVE source.
- Aug 19, 2026Record 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=6.1.0 <publication
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