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

Microsoft Windows User Profile Service Privilege Escalation

CVE-2022-26904 is a medium-severity concurrent execution using shared resource with improper synchronization vulnerability in Windows 10 Version 1809 from Microsoft, with a CVSS 2.0 base score of 4.4 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 25, 2022, which means attacks have been observed in the wild.

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
MediumSome conditions must be met.
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:M/Au:N/C:P/I:P/A:P. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.0HighCNA (microsoft.com)
CVSS 2.04.4MediumNVD

Official description

Windows User Profile Service Elevation of Privilege Vulnerability

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

The underlying weakness: Concurrent Execution using Shared Resource with Improper Synchronization

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

How developers prevent this class of flaw

  • In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.
  • Use thread-safe capabilities such as the data access abstraction in Spring.
  • Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring. Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).

More Concurrent Execution using Shared Resource with Improper Synchronization vulnerabilities (CWE-362)

Timeline

  1. CVE record published.
  2. Added to CISA's Known Exploited Vulnerabilities catalogue.
  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 Concurrent Execution using Shared Resource with Improper Synchronization vulnerabilities

Spotted an error? Tell us.