Code execution via malicious dump-file debugging
Published Jun 11, 2024 · Updated Aug 10, 2026
Remote code execution in Microsoft Visual Studio 2017, 2019, and 2022 allows local users to execute code by debugging a crafted dump file. The debugger processes an attacker-supplied file with an appropriate extension embedded in the dump, but Microsoft has not disclosed the exact parser or failed protection check. Exploitation requires the target user to open and debug the crafted dump, and successful exploitation can modify data or code in that user's security context.
Summary
What happened
Remote code execution in Microsoft Visual Studio 2017, 2019, and 2022 allows local users to execute code by debugging a crafted dump file. The debugger processes an attacker-supplied file with an appropriate extension embedded in the dump, but Microsoft has not disclosed the exact parser or failed protection check. Exploitation requires the target user to open and debug the crafted dump, and successful exploitation can modify data or code in that user's security context.
The record
- CVE
- CVE-2024-30052
- Published
- Jun 11, 2024
- Updated
- Aug 10, 2026
- Vendor
- Microsoft
- Product
- Microsoft Visual Studio 2019
- Classifications
- CWE-693, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2024CVE publishedPublication date reported by the CVE source.
- Aug 10, 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.37
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