Code execution via out-of-bounds memory write
Published Jan 14, 2020 · Updated Aug 4, 2024
Memory corruption in Microsoft Internet Explorer 9, 10, and 11 allows remote attackers to execute code through crafted web content. The browser performs an out-of-bounds write by improperly accessing objects in memory, but Microsoft has not disclosed a narrower code locus. Exploitation requires user interaction and high-complexity conditions, with successful attacks executing code in the affected browser context.
Summary
What happened
Memory corruption in Microsoft Internet Explorer 9, 10, and 11 allows remote attackers to execute code through crafted web content. The browser performs an out-of-bounds write by improperly accessing objects in memory, but Microsoft has not disclosed a narrower code locus. Exploitation requires user interaction and high-complexity conditions, with successful attacks executing code in the affected browser context.
The record
- CVE
- CVE-2020-0640
- Published
- Jan 14, 2020
- Updated
- Aug 4, 2024
- Vendor
- Microsoft
- Product
- Internet Explorer 10
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 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=Windows Server 2012
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.
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