Code execution via corrupted PDB heap overflow
Published Jun 14, 2023 · Updated Jan 1, 2025
Heap-based buffer overflow in the MSDIA SDK used by Microsoft .NET and Visual Studio allows local users to execute code via a malicious PDB file. The debugging-symbol reader mishandles corrupted PDB data and overruns a heap allocation while parsing the file. Exploitation requires user interaction with the crafted file; resulting memory corruption can crash the process or run attacker-controlled code.
Summary
What happened
Heap-based buffer overflow in the MSDIA SDK used by Microsoft .NET and Visual Studio allows local users to execute code via a malicious PDB file. The debugging-symbol reader mishandles corrupted PDB data and overruns a heap allocation while parsing the file. Exploitation requires user interaction with the crafted file; resulting memory corruption can crash the process or run attacker-controlled code.
The record
- CVE
- CVE-2023-24897
- Published
- Jun 14, 2023
- Updated
- Jan 1, 2025
- Vendor
- Microsoft
- Product
- Microsoft Visual Studio 2019
- Classifications
- CWE-122, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 14, 2023CVE publishedPublication date reported by the CVE source.
- Jan 1, 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.27
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