Browser memory disclosure via mishandled objects
Published Jun 9, 2020 · Updated Aug 4, 2024
Information disclosure in Microsoft Internet Explorer 9 and 11 allows remote attackers to read process memory through crafted web content. Microsoft states only that Internet Explorer improperly handles objects in memory and has not published the affected function or incorrect memory operation. Exploitation requires a user to interact with attacker-controlled content, and the documented consequence is disclosure without data modification or service interruption.
Summary
What happened
Information disclosure in Microsoft Internet Explorer 9 and 11 allows remote attackers to read process memory through crafted web content. Microsoft states only that Internet Explorer improperly handles objects in memory and has not published the affected function or incorrect memory operation. Exploitation requires a user to interact with attacker-controlled content, and the documented consequence is disclosure without data modification or service interruption.
The record
- CVE
- CVE-2020-1315
- Published
- Jun 9, 2020
- Updated
- Aug 4, 2024
- Vendor
- Microsoft
- Product
- Internet Explorer 11
- Classifications
- T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 9, 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
- Affected versionversion=Windows 10 for 32-bit Systems
- Affected versionversion=Windows 10 for x64-based Systems
- Affected versionversion=Windows 10 Version 1607 for 32-bit Systems
- Affected versionversion=Windows 10 Version 1607 for x64-based Systems
- Affected versionversion=Windows 10 Version 1709 for 32-bit Systems
- Affected versionversion=Windows 10 Version 1709 for ARM64-based Systems
- Affected versionversion=Windows 10 Version 1709 for x64-based Systems
- Affected versionversion=Windows 10 Version 1803 for 32-bit Systems
- Affected versionversion=Windows 10 Version 1803 for ARM64-based Systems
- Affected versionversion=Windows 10 Version 1803 for x64-based Systems
- Affected versionversion=Windows 10 Version 1809 for 32-bit Systems
- Affected versionversion=Windows 10 Version 1809 for ARM64-based Systems
- Affected versionversion=Windows 10 Version 1809 for x64-based Systems
- Affected versionversion=Windows 7 for 32-bit Systems Service Pack 1
- Affected versionversion=Windows 7 for x64-based Systems Service Pack 1
- Affected versionversion=Windows 8.1 for 32-bit systems
- Affected versionversion=Windows 8.1 for x64-based systems
- Affected versionversion=Windows RT 8.1
- Affected versionversion=Windows Server 2008 R2 for x64-based Systems Service Pack 1
- Affected versionversion=Windows Server 2012 R2
- Affected versionversion=Windows Server 2016
- Affected versionversion=Windows Server 2019
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