What is the CVSS score of CVE-2024-20656?

CVE-2024-20656 has a CVSS 3.1 base score of 7.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 54.3%.

Which versions of Visual Studio are affected by CVE-2024-20656?

CVE-2024-20656 presents notable security risk rated CVSS 7.8. Exploitation could compromise the security of affected deployments.. A patch is available.

How to fix or mitigate CVE-2024-20656?

Within 30 days: Identify all affected systems and apply vendor patches as part of regular patch cycle. Vendor patch is available.

Visual Studio CVE-2024-20656

HIGH

Improper Link Resolution Before File Access (CWE-59)

2024-01-09 secure@microsoft.com

Information Disclosure Visual Studio Visual Studio 2017 Visual Studio 2019 Visual Studio 2022

7.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.8 HIGH

AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 19:34 vuln.today

Patch released

Mar 28, 2026 - 19:34 nvd

Patch available

CVE Published

Jan 09, 2024 - 18:15 nvd

HIGH 7.8

DescriptionCVE.org

Visual Studio Elevation of Privilege Vulnerability

AnalysisAI

Visual Studio contains an elevation of privilege vulnerability that allows local attackers to escalate privileges through symlink exploitation. Successful exploitation grants elevated permissions on the development workstation, potentially compromising the software supply chain.

Technical ContextAI

The vulnerability exploits improper symlink handling in Visual Studio operations. A local attacker can create symbolic links that redirect Visual Studio file operations to privileged locations, achieving write access to protected system areas. This can be leveraged for privilege escalation or code injection into the Visual Studio build pipeline.

RemediationAI

Apply the January 2024 Microsoft security update. Implement least-privilege access on developer workstations. Monitor build environments for unexpected symlinks. Use build verification and code signing for release pipelines.