Local privilege escalation
Published Apr 11, 2023 · Updated Jan 23, 2025
Heap-based buffer overflow in Microsoft Visual Studio 2019 and 2022 affected releases allows local users to elevate privileges. Microsoft identifies the weakness as a heap-based buffer overflow but has not disclosed the affected component, triggering input, or out-of-bounds operation. Exploitation requires existing low-privilege local access and no user interaction, and successful exploitation grants an elevated but otherwise undisclosed security context on the Windows host.
Summary
What happened
Heap-based buffer overflow in Microsoft Visual Studio 2019 and 2022 affected releases allows local users to elevate privileges. Microsoft identifies the weakness as a heap-based buffer overflow but has not disclosed the affected component, triggering input, or out-of-bounds operation. Exploitation requires existing low-privilege local access and no user interaction, and successful exploitation grants an elevated but otherwise undisclosed security context on the Windows host.
The record
- CVE
- CVE-2023-28262
- Published
- Apr 11, 2023
- Updated
- Jan 23, 2025
- Vendor
- Microsoft
- Product
- Microsoft Visual Studio 2019
- Classifications
- CWE-122, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 11, 2023CVE publishedPublication date reported by the CVE source.
- Jan 23, 2025Record 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=16.11.0 <16.11.26
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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