CVE-2024-43590 json
Visual C++ Redistributable Installer Elevation of Privilege Vulnerability
published 2024-10-08 2 y ago modified 2026-08-19 2 mo ago also EUVD-2024-40342
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 37%
- public exploits
- 0
- none known
Summary
Visual C++ Redistributable Installer Elevation of Privilege Vulnerability
Patch / fix
- Microsoft Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8) 15.9.67
- Microsoft Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10) 16.11.41
- Microsoft Microsoft Visual Studio 2022 version 17.10 17.10.8
- Microsoft Microsoft Visual Studio 2022 version 17.11 17.11.5
- Microsoft Microsoft Visual Studio 2022 version 17.6 17.6.20
- Microsoft Microsoft Visual Studio 2022 version 17.8 17.8.15
- Microsoft Visual C++ Redistributable Installer 14.40.33816
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
0.43% chance of exploitation in the next 30 days, higher than 37% 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 2019 version 16.11 (includes 16.0 - 16.10)
- Microsoft Microsoft Visual Studio 2022 version 17.10
- Microsoft Microsoft Visual Studio 2022 version 17.11
- Microsoft Microsoft Visual Studio 2022 version 17.6
- Microsoft Microsoft Visual Studio 2022 version 17.8
- Microsoft Visual C++ Redistributable Installer
Classification
- Weakness
-
- CWE-284 Improper Access Control
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2024-43590
vendor-advisory, patch
Sources
- CVE List CVE-2024-43590
- NVD CVE-2024-43590
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.