← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2023-38180 exploited? Yes: in CISA KEV since 9 Aug 2023

Gociux · Microsoft .NET Core and Visual Studio · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2023-38180, Microsoft .NET Core and Visual Studio Denial-of-Service Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 9 Aug 2023, 1 days after it was published. It affects Microsoft .NET Core and Visual Studio. If you run it, CISA's required action is: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

exploitedYesCISA KEV · 9 Aug 2023
ransomwareNot knownno confirmed use
EPSStop 5%very likely to be exploited
severity7.5CVSS 3.1 · high
US federal due30 Aug 2023BOD 22-01 deadline

What it is

Microsoft .NET Core and Visual Studio contain an unspecified vulnerability that allows for denial-of-service (DoS).

VendorMicrosoft (391 exploited CVEs in KEV)
Product.NET Core and Visual Studio
VulnerabilityMicrosoft .NET Core and Visual Studio Denial-of-Service Vulnerability
Weaknessnot specified
Published8 Aug 2023
Added to KEV9 Aug 2023
Reported by (CNA)microsoft

What to do

  1. Check whether you run it. Look for .NET Core and Visual Studio in your asset inventory, including appliances and cloud images. Stack check lists every exploited Microsoft CVE at once.
  2. Apply the fix. Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 8 Aug 2023.
  4. Get told next time. Email alerts when CISA adds a CVE for Microsoft.

References

Questions

Is CVE-2023-38180 being exploited?

Yes. CISA added CVE-2023-38180 to the Known Exploited Vulnerabilities catalog on 9 Aug 2023, which means there is reliable evidence of exploitation in the wild.

Is CVE-2023-38180 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2023-38180?

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Check Microsoft's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected .NET Core and Visual Studio and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in August 2023 · Microsoft scorecard · act-now radar.

Running Microsoft in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →