Skip to content
Server Security Center
KEVhigh7.8

CVE-2024-49138: Microsoft Windows Common Log File System (CLFS) Driver Heap-Based Buffer Overflow

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2024-12-10.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
26%
higher than 98% of all CVEs
Added to CISA KEV
2024-12-10
US federal due date 2024-12-31
Automatable (CISA SSVC)
no
technical impact: total

CVE-2024-49138 explained

CVE-2024-49138 is a heap-based buffer overflow in the Microsoft Windows Common Log File System (CLFS) driver. A local attacker with low privileges can use it to escalate privileges. CISA lists it as known to be exploited, which makes prompt patching of affected Windows client and server systems important.

Impact

An attacker who can already run code on a system with low privileges can escalate privileges. No user interaction is required and attack complexity is low. Confidentiality, integrity and availability impact are all high. CISA rates the technical impact as total, meaning full control of the affected component. CISA rates it as not automatable, so exploitation needs manual steps per target. Attackers are known to exploit it; ransomware use is listed as unknown.

Who is affected

The CVE record lists Windows 10 versions 1507, 1607, 1809, 21H2 and 22H2, Windows 11 versions 22H2, 22H3, 23H2 and 24H2, Windows Server 2008 Service Pack 2, and Windows Server 2008 R2 Service Pack 1 including Server Core. Fixed builds include 10.0.19045.5247 (Windows 10 22H2), 10.0.22631.4602 (Windows 11 23H2), 10.0.26100.2605 (Windows 11 24H2), 6.0.6003.23016 (Server 2008 SP2) and 6.1.7601.27467 (Server 2008 R2 SP1). Further products are listed on this page.

Written with AI from the data on this page and checked against it automatically.

Official description

Microsoft Windows Common Log File System (CLFS) driver contains a heap-based buffer overflow vulnerability that allows a local attacker to escalate privileges.

CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.20857
    Fixed in
    • 10.0.10240.20857
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.7606
    Fixed in
    • 10.0.14393.7606
  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.6659
    Fixed in
    • 10.0.17763.6659
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.5247
    Fixed in
    • 10.0.19044.5247
  • Microsoft Windows 10 Version 22H232-bit, ARM64, x64
    Affected
    • < 10.0.19045.5247
    Fixed in
    • 10.0.19045.5247
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.4602
    Fixed in
    • 10.0.22621.4602
  • Microsoft Windows 11 version 22H3ARM64
    Affected
    • < 10.0.22631.4602
    Fixed in
    • 10.0.22631.4602
  • Microsoft Windows 11 Version 23H2x64
    Affected
    • < 10.0.22631.4602
    Fixed in
    • 10.0.22631.4602
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.2605
    Fixed in
    • 10.0.26100.2605
  • Microsoft Windows Server 2008 Service Pack 2x64, 32-bit
    Affected
    • < 6.0.6003.23016
    Fixed in
    • 6.0.6003.23016
Show 15 more products
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.27467
    Fixed in
    • 6.1.7601.27467
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.27467
    Fixed in
    • 6.1.7601.27467
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.23016
    Fixed in
    • 6.0.6003.23016
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.25222
    Fixed in
    • 6.2.9200.25222
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.25222
    Fixed in
    • 6.2.9200.25222
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.22318
    Fixed in
    • 6.3.9600.22318
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.22318
    Fixed in
    • 6.3.9600.22318
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.7606
    Fixed in
    • 10.0.14393.7606
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.7606
    Fixed in
    • 10.0.14393.7606
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.6659
    Fixed in
    • 10.0.17763.6659
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.6659
    Fixed in
    • 10.0.17763.6659
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.2966
    Fixed in
    • 10.0.20348.2966
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    • < 10.0.25398.1308
    Fixed in
    • 10.0.25398.1308
  • Microsoft Windows Server 2025x64
    Affected
    • < 10.0.26100.2605
    Fixed in
    • 10.0.26100.2605
  • Microsoft Windows Server 2025 (Server Core installation)x64
    Affected
    • < 10.0.26100.2605
    Fixed in
    • 10.0.26100.2605

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1507: 10.0.10240.20857
    • Microsoft Windows 10 Version 1607: 10.0.14393.7606
    • Microsoft Windows 10 Version 1809: 10.0.17763.6659
    • Microsoft Windows 10 Version 21H2: 10.0.19044.5247
    • Microsoft Windows 10 Version 22H2: 10.0.19045.5247
    • Microsoft Windows 11 version 22H2: 10.0.22621.4602
    Fixed versions for 19 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2024-49138
  • CISA's deadline for US federal agencies: 2024-12-31 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install Microsoft's security update so each system reaches at least the fixed build listed for its Windows version.
  2. Prioritize patching, since CISA lists this vulnerability as known exploited; the US federal due date was 2024-12-31.
  3. Follow the Microsoft vendor advisory for the full list of affected products and updates.
  4. Limit local and low-privileged access to systems, and remove unnecessary user accounts.
  5. Check unpatched or recently patched systems for signs of compromise, such as unexpected privileged accounts or processes.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-122 Heap-based Buffer Overflow

Questions about CVE-2024-49138

Can this be exploited remotely?
No. The attack vector is local. An attacker needs low-privileged access to the system first, then can escalate privileges. No user interaction is needed.
Is this vulnerability being exploited?
Yes. CISA added CVE-2024-49138 to its Known Exploited Vulnerabilities catalog on 2024-12-10. Whether it is used in ransomware campaigns is listed as unknown.
Which build fixes Windows 11 Version 24H2?
The CVE record lists 10.0.26100.2605 as the fixed version for Microsoft Windows 11 Version 24H2. Earlier builds are affected.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.