Skip to content
Server Security Center
KEVhigh7.8 Used in ransomware campaigns

CVE-2022-37969: Microsoft Windows Common Log File System (CLFS) Driver Privilege Escalation

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2022-09-14.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
28%
higher than 98.1% of all CVEs
Added to CISA KEV
2022-09-14
US federal due date 2022-10-05
Automatable (CISA SSVC)
no
technical impact: total

CVE-2022-37969 explained

CVE-2022-37969 is a privilege escalation vulnerability in the Microsoft Windows Common Log File System (CLFS) driver, classified as an out-of-bounds write. It affects many Windows 10, Windows 11 and Windows Server releases. CISA lists it as known exploited, including use in ransomware campaigns, which makes prompt patching important.

Impact

An attacker who already has low-privileged local access can exploit the flaw without user interaction to gain elevated privileges. Confidentiality, integrity and availability impacts are all high. CISA rates the technical impact as total, meaning full control of the affected system component. CISA does not consider it automatable, so exploitation requires an attacker to act on each target. Attackers are known to use it, including in ransomware attacks.

Who is affected

The record lists Windows 10 Version 1507, 1607, 1809, 20H2, 21H1 and 21H2, Windows 11 version 21H2, and Windows Server 2016, 2019 and 2022, including Server Core installations. Fixed builds include 10.0.17763.3406 (1809, Server 2019), 10.0.19043.2006 (21H1), 10.0.19042.2006 (20H2), 10.0.19044.2006 (21H2), 10.0.20348.1006 (Server 2022), 10.0.22000.978 (Windows 11 21H2), 10.0.10240.19444 (1507) and 10.0.14393.5356 (1607, Server 2016). 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 an unspecified vulnerability that allows for privilege escalation.

CISA required action: Apply updates per vendor instructions.

CISA notes

Affected and fixed versions

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

  • Microsoft Windows 10 Version 180932-bit, x64, ARM64
    Affected
    • < 10.0.17763.3406
    Fixed in
    • 10.0.17763.3406
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.3406
    Fixed in
    • 10.0.17763.3406
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.3406
    Fixed in
    • 10.0.17763.3406
  • Microsoft Windows 10 Version 21H1x64, ARM64, 32-bit
    Affected
    • < 10.0.19043.2006
    Fixed in
    • 10.0.19043.2006
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.1006
    Fixed in
    • 10.0.20348.1006
  • Microsoft Windows 10 Version 20H232-bit, ARM64
    Affected
    • < 10.0.19042.2006
    Fixed in
    • 10.0.19042.2006
  • Microsoft Windows 11 version 21H2x64, ARM64
    Affected
    • < 10.0.22000.978
    Fixed in
    • 10.0.22000.978
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.2006
    Fixed in
    • 10.0.19044.2006
  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.19444
    Fixed in
    • 10.0.10240.19444
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.5356
    Fixed in
    • 10.0.14393.5356
Show 13 more products
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.5356
    Fixed in
    • 10.0.14393.5356
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.5356
    Fixed in
    • 10.0.14393.5356
  • Microsoft Windows 732-bit
    Affected
    • < 6.1.7601.26115
    Fixed in
    • 6.1.7601.26115
  • Microsoft Windows 7 Service Pack 1x64
    Affected
    • < 6.1.7601.26115
    Fixed in
    • 6.1.7601.26115
  • Microsoft Windows 8.132-bit, x64, ARM64
    Affected
    • < 6.3.9600.20571
    Fixed in
    • 6.3.9600.20571
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • < 6.0.6003.21666
    Fixed in
    • 6.0.6003.21666
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.21666
    Fixed in
    • 6.0.6003.21666
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.26115
    Fixed in
    • 6.1.7601.26115
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.26115
    Fixed in
    • 6.1.7601.26115
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.23865
    Fixed in
    • 6.2.9200.23865
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.23865
    Fixed in
    • 6.2.9200.23865
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.20571
    Fixed in
    • 6.3.9600.20571
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.20571
    Fixed in
    • 6.3.9600.20571

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1809: 10.0.17763.3406
    • Microsoft Windows Server 2019: 10.0.17763.3406
    • Microsoft Windows Server 2019 (Server Core installation): 10.0.17763.3406
    • Microsoft Windows 10 Version 21H1: 10.0.19043.2006
    • Microsoft Windows Server 2022: 10.0.20348.1006
    • Microsoft Windows 10 Version 20H2: 10.0.19042.2006
    Fixed versions for 17 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2022-37969
  • CISA's deadline for US federal agencies: 2022-10-05 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update that brings each system to the fixed build listed for its Windows version.
  2. Prioritize servers and systems where many users have local access, since exploitation requires a local, low-privileged account.
  3. Verify installed build numbers across the fleet to confirm the update applied everywhere.
  4. Limit local and interactive logon rights to accounts that need them.
  5. Check systems for signs of compromise, given confirmed exploitation and ransomware use.
  6. Follow the Microsoft advisory for any additional guidance on listed products.

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-787 Out-of-bounds Write

Questions about CVE-2022-37969

Is CVE-2022-37969 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-09-14 and notes known use in ransomware campaigns. US federal agencies had to apply updates by 2022-10-05.
Can it be exploited remotely?
Not directly. The attack vector is local and requires low privileges. An attacker needs existing access to the system, then can escalate to higher privileges without user interaction.
What should we do to fix it?
Apply updates per Microsoft's instructions, as CISA requires. Make sure each system runs at least the fixed build listed for its Windows version.

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-22. Always confirm with the vendor's or distribution's advisory before patching.