Patch tracker / CVE reference / CVE-2024-38167

CVE-2024-38167

CVE-2024-38167 is a medium severity Microsoft vulnerability with a CVSS score of 6.5. Microsoft has shipped the fix: deploy the update below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

Medium

6.5

CVSS v3

2.7%

EPSS, 30 days

Medium

Severity

Not in the CISA KEV catalog. EPSS exploit probability 2.7%. CVSS 6.5 (Medium).

This CVE is among the lower half of tracked Microsoft CVEs by EPSS exploit probability.

Senserva AI Opinion for CVE-2024-38167

.NET 8.0 and Visual Studio 2022 (versions 17.8 and 17.10) share an information disclosure vulnerability here, rated High at 7.5 with a low 3 percent EPSS score, making it a developer-workstation concern rather than a server-fleet emergency. This is one of the few findings in this batch that targets development tooling rather than the Windows OS or a server role, so its exposure is limited to machines where developers build or debug .NET applications. It is not confirmed exploited or ransomware-linked.

Do this: Update Visual Studio 2022 and the .NET 8.0 SDK on developer workstations during the normal patch cycle.

AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2024-38167

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I am an IT admin assessing a vulnerability. Facts for CVE-2024-38167 (source: https://senserva.com/cve/CVE-2024-38167.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2024-38167: Medium severity Microsoft vulnerability, CVSS 6.5
- EPSS 30-day exploitation probability: 2.7%
- Actively exploited (CISA KEV): no
- Fixed by: KB5042132
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) What to patch or mitigate first. 4) How to check whether my devices are exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Schedule normally

No exploitation observed: not in the CISA KEV catalog, EPSS 3%.

Fixed by KB5042132. Download from the Microsoft Update Catalog, or deploy via Windows Update, Intune, or WSUS.

Do this now: Deploy with your normal update cycle. This page refreshes daily; the verdict changes the day the data does.

Official patch(es) for CVE-2024-38167

Lower priority: patch in your normal cycle. In Intune or Defender, confirm whether the fixing update KB5042132 are installed across the affected products. Senserva does this automatically across your tenant and flags every missing patch.

Apply the Microsoft security update below to fix CVE-2024-38167. Each KB page carries the Microsoft Update Catalog download, Microsoft's known issues for the update, a copy-paste PowerShell check for whether it is installed, and the Senserva AI read.

KB5042132

Scope and sources

Affected products

Fixed by the same update

CVE-2024-38168

Authoritative references

Official CVE record (cve.org)NVD detail Microsoft MSRC FIRST.org EPSS

Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.