Skip to content
Fencer Intel
medium 5.5

CVE-2024-43603 json

Visual Studio Collector Service Denial of Service Vulnerability

published 2y ago modified 2mo ago also EUVD-2024-40354

cvss
5.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits
0
none known

Summary

Visual Studio Collector Service Denial of Service Vulnerability

Patch / fix

  • Microsoft Microsoft Visual Studio 2015 Update 3 14.0.27561.00
  • 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

Is CVE-2024-43603 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

0.77% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Microsoft Microsoft Visual Studio 2015 Update 3
  • 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

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access

References

Sources

Fencer Intel 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.