CVE-2024-38178
Microsoft Windows Scripting Engine Memory Corruption
- Published13 Aug 2024
- Added to CISA KEV13 Aug 2024
- Remediation due3 Sept 2024
Description
Scripting Engine Memory Corruption Vulnerability
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2024-38178 being actively exploited?
Yes. CVE-2024-38178 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 13 Aug 2024.
How severe is CVE-2024-38178?
CVE-2024-38178 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 41.4% probability of exploitation.
Which products are affected by CVE-2024-38178?
Affected products include Microsoft Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 21h2, Microsoft Windows 10 22h2, and 9 more.
How do I fix CVE-2024-38178?
Upgrade affected software to a fixed version, for example Microsoft Windows 10 1507 10.0.10240.20751, Microsoft Windows 10 1607 10.0.14393.7259, Microsoft Windows 10 1809 10.0.17763.6189 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2024-38178 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, a risk for it never ranks below high, and the update that fixes it moves to the Emergency patch lane. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.