This page was not yet optimized for use on mobile devices.
CVE-2022-35825
Data ?
Vulnerability ID | CVE-2022-35825 |
---|---|
Published on | 09.08.2022 20:15 |
Severity | HIGH |
Vulnerable configurations ?
- cpe:2.3:a:microsoft:visual_studio:2012:update_5:*:*:*:*:*:*
- cpe:2.3:a:microsoft:visual_studio:2013:update_5:*:*:*:*:*:*
- cpe:2.3:a:microsoft:visual_studio:2015:update3:*:*:*:*:*:*
- cpe:2.3:a:microsoft:visual_studio_2017:15.9:*:*:*:*:*:*:*
- cpe:2.3:a:microsoft:visual_studio_2019:16.9:*:*:*:*:*:*:*
- cpe:2.3:a:microsoft:visual_studio_2019:16.11:*:*:*:*:*:*:*
- cpe:2.3:a:microsoft:visual_studio_2022:17.0:*:*:*:*:*:*:*
- cpe:2.3:a:microsoft:visual_studio_2022:17.2:*:*:*:*:*:*:*
Vulnerable certificates ?
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.