Local privilege escalation via memory mishandling
Published Jun 9, 2020 · Updated Aug 4, 2024
Memory mishandling in Windows Error Reporting in Microsoft Windows allows local users with code execution to elevate privileges. Microsoft states only that Windows Error Reporting improperly handles objects in memory and does not identify the affected function, object type, or unsafe operation. The attacker must first execute code on the target; the published impact is privilege elevation rather than remote initial access.
Summary
What happened
Memory mishandling in Windows Error Reporting in Microsoft Windows allows local users with code execution to elevate privileges. Microsoft states only that Windows Error Reporting improperly handles objects in memory and does not identify the affected function, object type, or unsafe operation. The attacker must first execute code on the target; the published impact is privilege elevation rather than remote initial access.
The record
- CVE
- CVE-2020-1234
- Published
- Jun 9, 2020
- Updated
- Aug 4, 2024
- Vendor
- Microsoft
- Product
- Windows 10 Version 1909
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
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
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