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

Published Apr 12, 2022
·
Updated

Windows Common Log File System Driver Elevation of Privilege Vulnerability

Other sources

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

CISA

Affected Software

76 affected componentsFixes available
Microsoft Windows 10=20H2
Microsoft Windows 10
Microsoft Windows 10=20h2
Microsoft Windows 10=21h1
Microsoft Windows 10=21h2
Microsoft Windows 10=1607
Microsoft Windows 10=1809
Microsoft Windows 10=1909
Microsoft Windows 11
Microsoft Windows 11
Microsoft Windows 7=sp1
Microsoft Windows 8.1
Microsoft Windows RT 8.1
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 2016=20h2
Microsoft Windows Server 2019
Microsoft Windows Server 2022
Microsoft Windows
Microsoft Windows 10 1507<10.0.10240.19265
Microsoft Windows 10 1607<10.0.14393.5066
Microsoft Windows 10 1809<=10.0.17763.2803
Microsoft Windows 10 1909<10.0.18363.2212
Microsoft Windows 10 20h2<10.0.19042.1645
Microsoft Windows 10 21h1<10.0.19043.1645
Microsoft Windows 10 21h2<10.0.19044.1645
Microsoft Windows 11 21h2<10.0.22000.613
Microsoft Windows Server 2016<10.0.14393.5066
Microsoft Windows Server 2019<10.0.17763.2803
Microsoft Windows Server 2022<10.0.20348.643
Microsoft Windows Server 20h2<10.0.19042.1645
Microsoft Windows Server 2008 R2<6.1.7601.25924
6.1.7601.25924
Microsoft Windows Server 2008 R2<6.1.7601.25924
6.1.7601.25924
Microsoft Windows Server 2008<6.0.6003.21446
6.0.6003.21446
Microsoft Windows Server 2008<6.0.6003.21446
6.0.6003.21446
Microsoft Windows Server 2008<6.0.6003.21446
6.0.6003.21446
Microsoft Windows Server 2008<6.0.6003.21446
6.0.6003.21446
Microsoft Windows RT 8.1<6.3.9600.20337
6.3.9600.20337
Microsoft Windows 8.1 for 32-bit systems<6.3.9600.20337
6.3.9600.20337
Microsoft Windows 7<6.1.7601.25924
6.1.7601.25924
Microsoft Windows 8.1 for x64-based systems<6.3.9600.20337
6.3.9600.20337
Microsoft Windows Server 2016<10.0.14393.5066
10.0.14393.5066
Microsoft Windows Server 2012<6.2.9200.23679
6.2.9200.23679
Microsoft Windows Server 2012 R2<6.3.9600.20337
6.3.9600.20337
Microsoft Windows Server 2012 R2<6.3.9600.20337
6.3.9600.20337
Microsoft Windows 7<6.1.7601.25924
6.1.7601.25924
Microsoft Windows 10=1607
10.0.14393.5066
Microsoft Windows Server 2012<6.2.9200.23679
6.2.9200.23679
Microsoft Windows Server 2016<10.0.14393.5066
10.0.14393.5066
Microsoft Windows 10<10.0.10240.19265
10.0.10240.19265
Microsoft Windows 10<10.0.10240.19265
10.0.10240.19265
Microsoft Windows 10=1607
10.0.14393.5066
Microsoft Windows 10=21H2
10.0.19044.1645
Microsoft Windows 11=21H2
10.0.22000.613
Microsoft Windows 11=21H2
10.0.22000.613
Microsoft Windows 10=21H2
10.0.19044.1645
Microsoft Windows Server=20H2
10.0.19042.1645
Microsoft Windows 10=21H2
10.0.19044.1645
Microsoft Windows 10=20H2
10.0.19042.1645
Microsoft Windows 10=21H1
10.0.19043.1645
Microsoft Windows Server 2022<10.0.20348.643
10.0.20348.643
Microsoft Windows 10=21H1
10.0.19043.1645
Microsoft Windows 10=1909
10.0.18363.2212
Microsoft Windows 10=21H1
10.0.19043.1645
Microsoft Windows Server 2019<10.0.17763.2803
10.0.17763.2803
Microsoft Windows 10=20H2
10.0.19042.1645
Microsoft Windows 10=1909
10.0.18363.2212
Microsoft Windows Server 2019<10.0.17763.2803
10.0.17763.2803
Microsoft Windows 10=1809
10.0.17763.2803
Microsoft Windows 10=1909
10.0.18363.2212
Microsoft Windows 10=1809
10.0.17763.2803
Microsoft Windows Server 2022<10.0.20348.643
10.0.20348.643
Microsoft Windows 10=1809
10.0.17763.2803

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.1.7601.25924Patch KB5012649
  2. Upgrade

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

    Fixed in 6.0.6003.21446Patch KB5012632
  3. Upgrade

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

    Fixed in 6.3.9600.20337Patch KB5012670
  4. Upgrade

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

    Fixed in 6.3.9600.20337Patch KB5012639
  5. Upgrade

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

    Fixed in 10.0.14393.5066Patch KB5012596
  6. Upgrade

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

    Fixed in 6.2.9200.23679Patch KB5012666
  7. Upgrade

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

    Fixed in 10.0.10240.19265Patch KB5012653
  8. Upgrade

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

    Fixed in 10.0.19044.1645Patch KB5012599
  9. Upgrade

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

    Fixed in 10.0.22000.613Patch KB5012592
  10. Upgrade

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

    Fixed in 10.0.19042.1645Patch KB5012599
  11. Upgrade

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

    Fixed in 10.0.19043.1645Patch KB5012599
  12. Upgrade

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

    Fixed in 10.0.20348.643Patch KB5012604
  13. Upgrade

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

    Fixed in 10.0.18363.2212Patch KB5012591
  14. Upgrade

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

    Fixed in 10.0.17763.2803Patch KB5012647

Event History

Apr 12, 2022
CVE Published
via Microsoft·08:00 AM
Known Exploited
via Microsoft·08:00 AM
Data Sourced
via Microsoft·08:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:00 AM
Affected Software
Updated
via Microsoft·08:00 AM
Description
Apr 13, 2022
Known Ransomware
via CISA·12:00 AM
Apr 15, 2022
CVE Published
via MITRE·07:03 PM
Data Sourced
via MITRE·07:03 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-24521?

CVE-2022-24521 has been rated as a critical vulnerability due to its potential to allow elevation of privilege.

2

How do I fix CVE-2022-24521?

To fix CVE-2022-24521, you should install the security updates provided by Microsoft on the affected Windows versions.

3

Which systems are affected by CVE-2022-24521?

CVE-2022-24521 affects multiple Windows versions, including Windows 10, Windows Server 2012 R2, and Windows 11 among others.

4

What details are available about CVE-2022-24521?

CVE-2022-24521 refers to a vulnerability in the Windows Common Log File System Driver that allows for elevation of privilege.

5

Is there a workaround for CVE-2022-24521?

There is no recommended workaround for CVE-2022-24521; the best practice is to apply the available patches.

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