cve.bz

CVE-2024-38063 microsoft: Integer Underflow (Wrap or Wraparound)

9.8 criticalEPSS 74%Fix available

Critical (9.8) in microsoft. EPSS 74% estimated probability of exploitation activity in the next 30 days.

On this page
Windows TCP/IP Remote Code Execution Vulnerability

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
74% (unchanged from 74% a week ago; 71% 30 days ago) estimated probability of exploitation activity in the next 30 days; 99th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: total, assessed 2024-08-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-191 Integer Underflow (Wrap or Wraparound)
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-38063 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-38063?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-38063?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-38063 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Windows 10 Version 1809from 10.0.17763.0 before 10.0.17763.6293
Microsoft Windows Server 2019from 10.0.17763.0 before 10.0.17763.6293
Microsoft Windows Server 2019 (Server Core installation)from 10.0.17763.0 before 10.0.17763.6293
Microsoft Windows Server 2022from 10.0.20348.0 before 10.0.20348.2700
Microsoft Windows 11 version 21H2from 10.0.0 before 10.0.22000.3197
Microsoft Windows 10 Version 21H2from 10.0.19043.0 before 10.0.19044.4780
Microsoft Windows 11 version 22H2from 10.0.22621.0 before 10.0.22621.4037
Microsoft Windows 10 Version 22H2from 10.0.19045.0 before 10.0.19045.4780
Microsoft Windows 11 version 22H3from 10.0.22631.0 before 10.0.22631.4037
Microsoft Windows 11 Version 23H2from 10.0.22631.0 before 10.0.22631.4037
Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)from 10.0.25398.0 before 10.0.25398.1085
Microsoft Windows 10 Version 1507from 10.0.10240.0 before 10.0.10240.20751
Microsoft Windows 10 Version 1607from 10.0.14393.0 before 10.0.14393.7259
Microsoft Windows Server 2016from 10.0.14393.0 before 10.0.14393.7259
Microsoft Windows Server 2016 (Server Core installation)from 10.0.14393.0 before 10.0.14393.7259
Microsoft Windows Server 2008 Service Pack 2from 6.0.6003.0 before 6.0.6003.22825
Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)from 6.0.6003.0 before 6.0.6003.22825
Microsoft Windows Server 2008 Service Pack 2from 6.0.6003.0 before 6.0.6003.22825
Microsoft Windows Server 2008 R2 Service Pack 1from 6.1.7601.0 before 6.1.7601.27277
Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)from 6.1.7601.0 before 6.1.7601.27277
Microsoft Windows Server 2012from 6.2.9200.0 before 6.2.9200.25031
Microsoft Windows Server 2012 (Server Core installation)from 6.2.9200.0 before 6.2.9200.25031
Microsoft Windows Server 2012 R2from 6.3.9600.0 before 6.3.9600.22134
Microsoft Windows Server 2012 R2 (Server Core installation)from 6.3.9600.0 before 6.3.9600.22134
Microsoft Windows 11 Version 24H2from 10.0.26100.0 before 10.0.26100.1457

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

4 more

References

Check your stackJSON