cve.bz

CVE-2023-36900 microsoft: Year 2038 problem, Y2K38, Y2038, Epochalypse

7.8 highEPSS 10%Fix available

High (7.8) in microsoft. EPSS 10% estimated probability of exploitation activity in the next 30 days.

On this page
Windows Common Log File System Driver Elevation of Privilege Vulnerability

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
10% (unchanged from 10% a week ago; 10% 30 days ago) estimated probability of exploitation activity in the next 30 days; 96th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-36900 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-36900?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-36900?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-2023-36900 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 1507from 10.0.10240.0 before 10.0.10240.20107
Microsoft Windows 10 Version 1607from 10.0.14393.0 before 10.0.14393.6167
Microsoft Windows 10 Version 1809from 10.0.17763.0 before 10.0.17763.4737
Microsoft Windows 10 Version 1809from 10.0.0 before 10.0.17763.4737
Microsoft Windows 10 Version 21H2from 10.0.19044.0 before 10.0.19044.3324
Microsoft Windows 10 Version 22H2from 10.0.19045.0 before 10.0.19045.3324
Microsoft Windows 11 version 21H2from 10.0.22000.0 before 10.0.22000.2295
Microsoft Windows 11 version 22H2from 10.0.22621.0 before 10.0.22621.2134
Microsoft Windows Server 2008 Service Pack 2from 6.0.6003.0 before 6.0.6003.22216
Microsoft Windows Server 2008 R2 Service Pack 1from 6.1.7601.0 before 6.1.7601.26664
Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)from 6.1.7601.0 before 6.1.7601.26664
Microsoft Windows Server 2008 Service Pack 2from 6.0.6003.0 before 6.0.6003.22216
Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)from 6.0.6003.0 before 6.0.6003.22216
Microsoft Windows Server 2012from 6.2.9200.0 before 6.2.9200.24414
Microsoft Windows Server 2012 (Server Core installation)from 6.2.9200.0 before 6.2.9200.24414
Microsoft Windows Server 2012 R2from 6.3.9600.0 before 6.3.9600.21503
Microsoft Windows Server 2012 R2 (Server Core installation)from 6.3.9600.0 before 6.3.9600.21503
Microsoft Windows Server 2016from 10.0.14393.0 before 10.0.14393.6167
Microsoft Windows Server 2016 (Server Core installation)from 10.0.14393.0 before 10.0.14393.6167
Microsoft Windows Server 2019from 10.0.17763.0 before 10.0.17763.4737
Microsoft Windows Server 2019 (Server Core installation)from 10.0.17763.0 before 10.0.17763.4737
Microsoft Windows Server 2022from 10.0.20348.0 before 10.0.20348.1906

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON