Service interruption via improper link resolution
Published Feb 14, 2023 · Updated Aug 19, 2026
Improper link resolution in Microsoft Visual Studio 2017, 2019, and 2022 allows local users to interrupt the IDE through crafted file-system links. Microsoft identifies link following before file access as the weakness but has not published the affected component, file operation, or link type. Exploitation requires local low-privileged access and user interaction, and the documented consequence is an interruption of Visual Studio.
Summary
What happened
Improper link resolution in Microsoft Visual Studio 2017, 2019, and 2022 allows local users to interrupt the IDE through crafted file-system links. Microsoft identifies link following before file access as the weakness but has not published the affected component, file operation, or link type. Exploitation requires local low-privileged access and user interaction, and the documented consequence is an interruption of Visual Studio.
The record
- CVE
- CVE-2023-21567
- Published
- Feb 14, 2023
- Updated
- Aug 19, 2026
- Vendor
- Microsoft
- Product
- Microsoft Visual Studio 2019
- Classifications
- CWE-59, T1499
- Attack vector
- local
- Privileges
- authenticated
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.
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