CVE-2024-20656 json
Visual Studio Elevation of Privilege Vulnerability
published 2024-01-09 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-18371
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.9%
- EPSS 3.9% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
Visual Studio Elevation of Privilege Vulnerability
Patch / fix
- Microsoft Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8) 15.9.59
- Microsoft Microsoft Visual Studio 2022 version 17.2 17.2.23
- Microsoft Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10) 16.11.33
- Microsoft Microsoft Visual Studio 2022 version 17.4 17.4.15
- Microsoft Microsoft Visual Studio 2022 version 17.6 17.6.11
- Microsoft Microsoft Visual Studio 2015 Update 3 14.0.27560.00
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
3.95% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C |
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Microsoft Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8)
- Microsoft Microsoft Visual Studio 2022 version 17.2
- Microsoft Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10)
- Microsoft Microsoft Visual Studio 2022 version 17.4
- Microsoft Microsoft Visual Studio 2022 version 17.6
- Microsoft Microsoft Visual Studio 2015 Update 3
Classification
- Weakness
-
- CWE-59 Improper Link Resolution Before File Access
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2024-20656
vendor-advisory, patch
Sources
- CVE List CVE-2024-20656
- NVD CVE-2024-20656
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.