Code execution via object memory corruption
Published Mar 12, 2020 · Updated Aug 4, 2024
Memory corruption in Microsoft ChakraCore and Edge Legacy allows remote attackers to execute code through crafted web content. Microsoft has disclosed only that the scripting engine mishandles objects in memory; no affected function or invalid operation is public. Exploitation requires user interaction and executes code with the current user's rights.
Summary
What happened
Memory corruption in Microsoft ChakraCore and Edge Legacy allows remote attackers to execute code through crafted web content. Microsoft has disclosed only that the scripting engine mishandles objects in memory; no affected function or invalid operation is public. Exploitation requires user interaction and executes code with the current user's rights.
The record
- CVE
- CVE-2020-0825
- Published
- Mar 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- Microsoft
- Product
- Microsoft Edge Legacy
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 12, 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.
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