Microsoft Visual Studio Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Last Year

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Version

2017 15.927
2019 16.1118
2017 Version 15.916
2019 16.013
2017 15.011

Grouping all affected versions of a specific product helps to determine existing issues. This makes it possible to determine vendors and products which need attention when it comes to remediations.

Remediation

Official Fix196
Temporary Fix0
Workaround0
Unavailable5
Not Defined12

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High3
Functional0
Proof-of-Concept50
Unproven95
Not Defined65

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined0
Physical0
Local32
Adjacent12
Network169

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined0
High1
Low61
None151

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined0
Required113
None100

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Last Year

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤20
≤30
≤42
≤514
≤625
≤768
≤871
≤928
≤105

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤20
≤30
≤45
≤516
≤648
≤789
≤837
≤914
≤104

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤20
≤31
≤49
≤539
≤629
≤766
≤840
≤924
≤105

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤31
≤41
≤52
≤610
≤79
≤847
≤99
≤106

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤20
≤30
≤41
≤52
≤69
≤711
≤844
≤923
≤101

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤41
≤53
≤610
≤716
≤876
≤928
≤102

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k0
<2k1
<5k13
<10k48
<25k124
<50k26
<100k1
≥100k0

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k132
<2k35
<5k30
<10k10
<25k6
<50k0
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Last Year

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Versions (84): 6, 6.0, 8.0, 17.0, 17.1, 17.2, 17.3, 17.4, 17.5, 17.6, 17.7, 2002, 2003, 2005, 2008, 2008 Express, 2010, 2010 SP1, 2012 Update 5, 2013 Update 5, 2015 Update 3, 2015 Update 5, 2017, 2017 15.0, 2017 15.1, 2017 15.2, 2017 15.3, 2017 15.4, 2017 15.5, 2017 15.6, 2017 15.7, 2017 15.8, 2017 15.9, 2017 Version 15.0, 2017 Version 15.1, 2017 Version 15.2, 2017 Version 15.3, 2017 Version 15.4, 2017 Version 15.5, 2017 Version 15.6, 2017 Version 15.7, 2017 Version 15.7.5, 2017 Version 15.8, 2017 Version 15.8 Preview, 2017 Version 15.9, 2019, 2019 16.0, 2019 16.1, 2019 16.2, 2019 16.3, 2019 16.4, 2019 16.5, 2019 16.6, 2019 16.7, 2019 16.8, 2019 16.9, 2019 16.10, 2019 16.11, 2019 Version 16.0, 2019 Version 16.1, 2019 Version 16.2, 2019 Version 16.3, 2019 Version 16.4, 2019 Version 16.5, 2019 Version 16.6, 2019 Version 16.7, 2019 Version 16.8, 2019 Version 16.9, 2019 version 16.0, 2019 version 16.1, 2019 version 16.2, 2019 version 16.3, 2019 version 16.4, 2020, 2022, 2022 17.0, 2022 17.1, 2022 17.2, 2022 17.3, 2022 17.4, 2022 17.5, 2022 17.6, 2022 17.7, 2022 17.15

Link to Product Website: https://www.microsoft.com/

Software Type: Programming Tool Software

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
05/14/20245.95.2Microsoft Visual Studio race condition$5k-$25k$0-$5kUnprovenOfficial Fix0.23CVE-2024-30046
05/14/20246.35.5Microsoft .NET/Visual Studio heap-based overflow$5k-$25k$0-$5kUnprovenOfficial Fix0.08CVE-2024-30045
04/09/20248.88.1Microsoft ODBC Driver/SQL Server/Visual Studio out-of-bounds$25k-$100k$5k-$25kUnprovenOfficial Fix0.06CVE-2024-28938
04/09/20248.87.7Microsoft ODBC Driver/SQL Server/Visual Studio heap-based overflow$25k-$100k$5k-$25kUnprovenOfficial Fix0.03CVE-2024-28937
04/09/20248.88.1Microsoft ODBC Driver/SQL Server/Visual Studio integer overflow$25k-$100k$5k-$25kUnprovenOfficial Fix0.06CVE-2024-28936
04/09/20248.88.1Microsoft ODBC Driver/SQL Server/Visual Studio heap-based overflow$25k-$100k$5k-$25kUnprovenOfficial Fix0.07CVE-2024-28935
04/09/20248.88.1Microsoft ODBC Driver/SQL Server/Visual Studio stack-based overflow$25k-$100k$5k-$25kUnprovenOfficial Fix0.04CVE-2024-28934
04/09/20248.88.1Microsoft ODBC Driver/SQL Server/Visual Studio integer underflow$25k-$100k$5k-$25kUnprovenOfficial Fix0.09CVE-2024-28933
04/09/20248.88.1Microsoft ODBC Driver/SQL Server/Visual Studio heap-based overflow$25k-$100k$5k-$25kUnprovenOfficial Fix0.03CVE-2024-28932
04/09/20248.88.1Microsoft ODBC Driver/SQL Server/Visual Studio integer overflow$25k-$100k$5k-$25kUnprovenOfficial Fix0.00CVE-2024-28931
04/09/20248.88.1Microsoft ODBC Driver/SQL Server/Visual Studio integer underflow$25k-$100k$5k-$25kUnprovenOfficial Fix0.06CVE-2024-28930
04/09/20248.88.1Microsoft ODBC Driver/SQL Server/Visual Studio integer overflow$25k-$100k$5k-$25kUnprovenOfficial Fix0.03CVE-2024-28929
04/09/20247.56.9Microsoft .NET/.NET Framework/Visual Studio use after free$5k-$25k$0-$5kUnprovenOfficial Fix0.09CVE-2024-21409
03/12/20248.88.1Microsoft Visual Studio Code Privilege Escalation$5k-$25k$0-$5kUnprovenOfficial Fix0.00CVE-2024-26165
03/12/20247.57.0Microsoft .NET/Visual Studio denial of service$5k-$25k$0-$5kProof-of-ConceptOfficial Fix0.06CVE-2024-21392
02/13/20247.57.0Microsoft Visual Studio/.NET denial of service$5k-$25k$0-$5kProof-of-ConceptOfficial Fix0.09CVE-2024-21404
02/13/20247.57.0Microsoft Visual Studio/ASP.NET Core denial of service$5k-$25k$5k-$25kProof-of-ConceptOfficial Fix0.04CVE-2024-21386
01/09/20246.86.2Microsoft .NET/Identity Model/Visual Studio denial of service$5k-$25k$0-$5kUnprovenOfficial Fix0.03CVE-2024-21319
01/09/20247.87.1Microsoft Visual Studio Local Privilege Escalation$5k-$25k$0-$5kUnprovenOfficial Fix0.03CVE-2024-20656
01/09/20248.88.4Microsoft .NET/.NET Framework/Visual Studio Remote Code Execution$5k-$25k$0-$5kProof-of-ConceptOfficial Fix0.06CVE-2024-0057
01/09/20248.07.3Microsoft .NET/.NET Framework/SQL Server/Visual Studio SQL Data Provider Remote Code Execution$5k-$25k$5k-$25kUnprovenOfficial Fix0.02CVE-2024-0056
12/29/20236.46.3Microsoft Python Extension for Visual Studio Code Remote Code Execution$5k-$25k$0-$5kNot DefinedOfficial Fix0.03CVE-2020-17163
11/14/20235.35.1Microsoft ASP.NET/.NET/Visual Studio information disclosure$5k-$25k$0-$5kProof-of-ConceptOfficial Fix0.00CVE-2023-36558
11/14/20238.17.7Microsoft .NET/.NET Framework/Visual Studio Privilege Escalation$5k-$25k$0-$5kProof-of-ConceptOfficial Fix0.06CVE-2023-36049
11/14/20235.85.5Microsoft Visual Studio denial of service$0-$5k$0-$5kUnprovenOfficial Fix0.03CVE-2023-36042

188 more entries are not shown

more entries by Microsoft

Do you know our Splunk app?

Download it now for free!