Code execution via incorrect captured-scope indexing
Published May 21, 2020 · Updated Aug 19, 2026
Memory corruption in Microsoft Edge Legacy and ChakraCore allows remote attackers to execute code via crafted JavaScript content. ScopeInfo.cpp omits an enclosing body scope when a nested function is declared in a merged parameter scope, causing captured symbols to receive an incorrect envIndex. Exploitation requires user interaction with attacker-controlled content and runs code with the current user's rights.
Summary
What happened
Memory corruption in Microsoft Edge Legacy and ChakraCore allows remote attackers to execute code via crafted JavaScript content. ScopeInfo.cpp omits an enclosing body scope when a nested function is declared in a merged parameter scope, causing captured symbols to receive an incorrect envIndex. Exploitation requires user interaction with attacker-controlled content and runs code with the current user's rights.
The record
- CVE
- CVE-2020-1065
- Published
- May 21, 2020
- Updated
- Aug 19, 2026
- Vendor
- Microsoft
- Product
- Microsoft Edge Legacy
- Classifications
- CWE-787, T1203
- Attack vector
- network
- 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=1.0..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.
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