CVE-2022-37969: Windows Common Log File System Driver Elevation of Privilege Vulnerability

Published Sep 13, 2022
·
Updated

Microsoft Windows Common Log File System (CLFS) driver contains an unspecified vulnerability that allows for privilege escalation.

Other sources

Windows Common Log File System Driver Elevation of Privilege Vulnerability

Affected Software

86 affected componentsFixes available
Microsoft Windows 10=20H2
Microsoft Windows 10
Microsoft Windows 10
Microsoft Windows 10=20h2
Microsoft Windows 10=20h2
Microsoft Windows 10=20h2
Microsoft Windows 10=21h1
Microsoft Windows 10=21h1
Microsoft Windows 10=21h1
Microsoft Windows 10=21h2
Microsoft Windows 10=21h2
Microsoft Windows 10=21h2
Microsoft Windows 10=1607
Microsoft Windows 10=1607
Microsoft Windows 10=1809
Microsoft Windows 10=1809
Microsoft Windows 10=1809
Microsoft Windows 11
Microsoft Windows 11
Microsoft Windows 7=sp1
Microsoft Windows 7=sp1
Microsoft Windows 8.1
Microsoft Windows 8.1
Microsoft Windows 8.1
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=r2-sp1
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
Microsoft Windows Server 2016
Microsoft Windows Server 2019
Microsoft Windows Server 2022
Microsoft Windows Server 2022
Microsoft Windows
Microsoft Windows 10 1507<10.0.10240.19444
Microsoft Windows 10 1607<10.0.14393.5356
Microsoft Windows 10 1809<10.0.17763.3406
Microsoft Windows 10 20h2<10.0.19042.2006
Microsoft Windows 10 21h1<10.0.19043.2006
Microsoft Windows 10 21h2<10.0.19044.2006
Microsoft Windows 11 21h2<10.0.22000.978
Microsoft Windows 7=sp1
Microsoft Windows 8.1
Microsoft Windows RT 8.1
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2016<10.0.14393.5356
Microsoft Windows Server 2019<10.0.17763.3406
Microsoft Windows Server 2022<10.0.20348.1006
Microsoft Windows Server 2008<6.0.6003.21666
6.0.6003.21666
Microsoft Windows Server 2012 R2<6.3.9600.20571
6.3.9600.20571
Microsoft Windows Server 2012 R2<6.3.9600.20571
6.3.9600.20571
Microsoft Windows Server 2012<6.2.9200.23865
6.2.9200.23865
Microsoft Windows Server 2008<6.0.6003.21666
6.0.6003.21666
Microsoft Windows Server 2012<6.2.9200.23865
6.2.9200.23865
Microsoft Windows Server 2008 R2<6.1.7601.26115
6.1.7601.26115
Microsoft Windows Server 2008<6.0.6003.21666
6.0.6003.21666
Microsoft Windows Server 2008<6.0.6003.21666
6.0.6003.21666
Microsoft Windows Server 2008 R2<6.1.7601.26115
6.1.7601.26115
Microsoft Windows RT 8.1<6.3.9600.20571
6.3.9600.20571
Microsoft Windows 8.1 for x64-based systems<6.3.9600.20571
6.3.9600.20571
Microsoft Windows 7<6.1.7601.26115
6.1.7601.26115
Microsoft Windows 7<6.1.7601.26115
6.1.7601.26115
Microsoft Windows 8.1 for 32-bit systems<6.3.9600.20571
6.3.9600.20571
Microsoft Windows Server 2016<10.0.14393.5356
10.0.14393.5356
Microsoft Windows 10=1607
10.0.14393.5356
Microsoft Windows 10<10.0.10240.19444
10.0.10240.19444
Microsoft Windows Server 2016<10.0.14393.5356
10.0.14393.5356
Microsoft Windows 10<10.0.10240.19444
10.0.10240.19444
Microsoft Windows 10=1607
10.0.14393.5356
Microsoft Windows 10=21H2
10.0.19044.2006
Microsoft Windows 10=21H2
10.0.19044.2006
Microsoft Windows 11=21H2
10.0.22000.978
Microsoft Windows 10=20H2
10.0.19042.2006
Microsoft Windows 10=21H2
10.0.19044.2006
Microsoft Windows 11=21H2
10.0.22000.978
Microsoft Windows Server 2022<10.0.20348.1006, <10.0.20348.916
10.0.20348.100610.0.20348.916
Microsoft Windows Server 2022<10.0.20348.1006, <10.0.20348.916
10.0.20348.100610.0.20348.916
Microsoft Windows 10=21H1
10.0.19043.2006
Microsoft Windows 10=21H1
10.0.19043.2006
Microsoft Windows 10=20H2
10.0.19042.2006
Microsoft Windows 10=21H1
10.0.19043.2006
Microsoft Windows Server 2019<10.0.17763.3406
10.0.17763.3406
Microsoft Windows 10=1809
10.0.17763.3406
Microsoft Windows Server 2019<10.0.17763.3406
10.0.17763.3406
Microsoft Windows 10=1809
10.0.17763.3406
Microsoft Windows 10=1809
10.0.17763.3406

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.0.6003.21666Patch KB5017371
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.3.9600.20571Patch KB5017365
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.2.9200.23865Patch KB5017377
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.1.7601.26115Patch KB5017373
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.3.9600.20571Patch KB5017367
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.14393.5356Patch KB5017305
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.10240.19444Patch KB5017327
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19044.2006Patch KB5017308
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.22000.978Patch KB5017328
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19042.2006Patch KB5017308
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.20348.1006Fixed in 10.0.20348.916Patch KB5017392
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19043.2006Patch KB5017308
  13. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.17763.3406Patch KB5017315

Event History

Sep 13, 2022
CVE Published
via Microsoft·07:00 AM
Known Exploited
via Microsoft·07:00 AM
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
Description
CVE Published
via MITRE·06:42 PM
Data Sourced
via MITRE·06:42 PM
DescriptionSeverity
Data Sourced
via NVD·07:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2022-37969?

CVE-2022-37969 is classified as a privilege escalation vulnerability in the Microsoft Windows Common Log File System driver.

2

How do I fix CVE-2022-37969?

To fix CVE-2022-37969, apply the relevant security updates provided by Microsoft for the affected Windows versions.

3

Which Windows versions are affected by CVE-2022-37969?

CVE-2022-37969 affects multiple versions of Windows including Windows Server 2016, 2019, Windows 10 (various builds), Windows 7, and Windows 8.1.

4

Can CVE-2022-37969 be exploited remotely?

CVE-2022-37969 requires local access to exploit, making it less likely to be exploited remotely.

5

What are the potential impacts of exploiting CVE-2022-37969?

Exploiting CVE-2022-37969 could allow an attacker to gain elevated privileges on the affected system.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203