CyberSecBulletin
CVE-2022-24521Exploited in the wildNVD status: Analyzed

Microsoft Windows CLFS Driver Privilege Escalation

CVE-2022-24521 is a medium-severity out-of-bounds write vulnerability in Windows 10 Version 1809 from Microsoft, with a CVSS 2.0 base score of 4.6 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, without any action from a user. The record lists version 10.0.17763.2803 as the first without the flaw, so updating Windows 10 Version 1809 to that release or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on April 13, 2022, which means attacks have been observed in the wild, including in ransomware campaigns.

Patch now

Attackers are already exploiting this vulnerability, according to CISA.

What to do

  1. Update Windows 10 Version 1809 to 10.0.17763.2803 or a later version.
  2. Update Windows Server 2019 to 10.0.17763.2803 or a later version.
  3. Update Windows Server 2019 (Server Core installation) to 10.0.17763.2803 or a later version.
  4. CISA's required action: Apply updates per vendor instructions.
  5. Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
MicrosoftWindows 10 Version 180910.0.17763.0 up to, but not including, 10.0.17763.2803; 10.0.0 up to, but not including, 10.0.17763.280310.0.17763.2803
MicrosoftWindows Server 201910.0.17763.0 up to, but not including, 10.0.17763.280310.0.17763.2803
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0 up to, but not including, 10.0.17763.280310.0.17763.2803
MicrosoftWindows 10 Version 190910.0.0 up to, but not including, 10.0.18363.221210.0.18363.2212
MicrosoftWindows 10 Version 21H110.0.0 up to, but not including, 10.0.19043.164510.0.19043.1645
MicrosoftWindows Server 202210.0.20348.0 up to, but not including, 10.0.20348.64310.0.20348.643
MicrosoftWindows 10 Version 20H210.0.0 up to, but not including, 10.0.19042.164510.0.19042.1645
MicrosoftWindows Server version 20H210.0.0 up to, but not including, 10.0.19042.164510.0.19042.1645
MicrosoftWindows 11 version 21H210.0.0 up to, but not including, 10.0.22000.61310.0.22000.613
MicrosoftWindows 10 Version 21H210.0.19043.0 up to, but not including, 10.0.19044.164510.0.19044.1645
MicrosoftWindows 10 Version 150710.0.10240.0 up to, but not including, 10.0.10240.1926510.0.10240.19265
MicrosoftWindows 10 Version 160710.0.14393.0 up to, but not including, 10.0.14393.506610.0.14393.5066
MicrosoftWindows Server 201610.0.14393.0 up to, but not including, 10.0.14393.506610.0.14393.5066
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0 up to, but not including, 10.0.14393.506610.0.14393.5066
MicrosoftWindows 76.1.0 up to, but not including, 6.1.7601.259246.1.7601.25924
MicrosoftWindows 7 Service Pack 16.1.0 up to, but not including, 6.1.7601.259246.1.7601.25924
MicrosoftWindows 8.16.3.0 up to, but not including, 6.3.9600.203376.3.9600.20337
MicrosoftWindows Server 2008 Service Pack 26.0.6003.0 up to, but not including, 6.0.6003.214466.0.6003.21446
MicrosoftWindows Server 2008 Service Pack 2 (Server Core installation)6.0.6003.0 up to, but not including, 6.0.6003.214466.0.6003.21446
MicrosoftWindows Server 2008 R2 Service Pack 16.1.7601.0 up to, but not including, 6.1.7601.259246.1.7601.25924
MicrosoftWindows Server 2008 R2 Service Pack 1 (Server Core installation)6.1.7601.0 up to, but not including, 6.1.7601.259246.1.7601.25924
MicrosoftWindows Server 20126.2.9200.0 up to, but not including, 6.2.9200.236796.2.9200.23679
MicrosoftWindows Server 2012 (Server Core installation)6.2.9200.0 up to, but not including, 6.2.9200.236796.2.9200.23679
MicrosoftWindows Server 2012 R26.3.9600.0 up to, but not including, 6.3.9600.203376.3.9600.20337
MicrosoftWindows Server 2012 R2 (Server Core installation)6.3.9600.0 up to, but not including, 6.3.9600.203376.3.9600.20337

Version data comes from the organisation that assigned the CVE; 11 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Access vector
LocalLocal access is required.
Access complexity
LowNo special conditions are needed.
Authentication
NoneNo login is needed.
Confidentiality
PartialSome data can be read.
Integrity
PartialSome data can be modified.
Availability
PartialAvailability is reduced.

Vector: AV:L/AC:L/Au:N/C:P/I:P/A:P. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.8HighCNA (microsoft.com)
CVSS 2.04.6MediumNVD

Official description

Windows Common Log File System Driver Elevation of Privilege Vulnerability

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Write

The product writes data past the end, or before the beginning, of the intended buffer.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Out-of-bounds Write vulnerabilities (CWE-787)

Timeline

  1. Added to CISA's Known Exploited Vulnerabilities catalogue.
  2. CVE record published.
  3. Deadline for US federal agencies to remediate, set by CISA.
  4. CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
  5. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.