Code execution via malicious debugging symbols
Published Feb 14, 2023 · Updated Aug 19, 2026
Use-after-free in the MSDIA SDK in .NET and Visual Studio allows context-dependent attackers to execute code through malicious debugging symbols. The debugging-symbol reader dereferences an untrusted pointer after its target memory has been freed, allowing crafted symbol data to corrupt process memory. Exploitation requires a user or application to read the malicious symbols, after which code executes in the consuming process's security context.
Summary
What happened
Use-after-free in the MSDIA SDK in .NET and Visual Studio allows context-dependent attackers to execute code through malicious debugging symbols. The debugging-symbol reader dereferences an untrusted pointer after its target memory has been freed, allowing crafted symbol data to corrupt process memory. Exploitation requires a user or application to read the malicious symbols, after which code executes in the consuming process's security context.
The record
- CVE
- CVE-2023-21808
- Published
- Feb 14, 2023
- Updated
- Aug 19, 2026
- Vendor
- Microsoft
- Product
- Microsoft Visual Studio 2019
- Classifications
- CWE-416, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 14, 2023CVE 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=16.11.0 <16.11.24
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.
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