CyberSecBulletin
CVE-2023-36874Exploited in the wildNVD status: Analyzed

Microsoft Windows Error Reporting Service Privilege Escalation

CVE-2023-36874 is a high-severity improper link resolution before file access vulnerability in Windows 10 Version 1809 from Microsoft, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists version 10.0.17763.4645 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 July 11, 2023, 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.4645 or a later version.
  2. Update Windows Server 2019 to 10.0.17763.4645 or a later version.
  3. Update Windows Server 2019 (Server Core installation) to 10.0.17763.4645 or a later version.
  4. CISA's required action: Apply updates per vendor instructions or discontinue use of the product if updates are unavailable.
  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.4645; 10.0.0 up to, but not including, 10.0.17763.464510.0.17763.4645
MicrosoftWindows Server 201910.0.17763.0 up to, but not including, 10.0.17763.464510.0.17763.4645
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0 up to, but not including, 10.0.17763.464510.0.17763.4645
MicrosoftWindows Server 202210.0.20348.0 up to, but not including, 10.0.20348.185010.0.20348.1850
MicrosoftWindows 11 version 21H210.0.0 up to, but not including, 10.0.22000.217610.0.22000.2176
MicrosoftWindows 10 Version 21H210.0.19043.0 up to, but not including, 10.0.19044.320810.0.19044.3208
MicrosoftWindows 11 version 22H210.0.22621.0 up to, but not including, 10.0.22621.199210.0.22621.1992
MicrosoftWindows 10 Version 22H210.0.19045.0 up to, but not including, 10.0.19045.320810.0.19045.3208
MicrosoftWindows 10 Version 150710.0.10240.0 up to, but not including, 10.0.10240.2004810.0.10240.20048
MicrosoftWindows 10 Version 160710.0.14393.0 up to, but not including, 10.0.14393.608510.0.14393.6085
MicrosoftWindows Server 201610.0.14393.0 up to, but not including, 10.0.14393.608510.0.14393.6085
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0 up to, but not including, 10.0.14393.608510.0.14393.6085
MicrosoftWindows Server 2008 Service Pack 26.0.6003.0 up to, but not including, 6.0.6003.221756.0.6003.22175
MicrosoftWindows Server 2008 Service Pack 2 (Server Core installation)6.0.6003.0 up to, but not including, 6.0.6003.221756.0.6003.22175
MicrosoftWindows Server 2008 R2 Service Pack 16.1.7601.0 up to, but not including, 6.1.7601.266236.1.7601.26623
MicrosoftWindows Server 2008 R2 Service Pack 1 (Server Core installation)6.1.7601.0 up to, but not including, 6.1.7601.266236.1.7601.26623
MicrosoftWindows Server 20126.2.9200.0 up to, but not including, 6.2.9200.243746.2.9200.24374
MicrosoftWindows Server 2012 (Server Core installation)6.2.9200.0 up to, but not including, 6.2.9200.243746.2.9200.24374
MicrosoftWindows Server 2012 R26.3.9600.0 up to, but not including, 6.3.9600.210636.3.9600.21063
MicrosoftWindows Server 2012 R2 (Server Core installation)6.3.9600.0 up to, but not including, 6.3.9600.210636.3.9600.21063
MicrosoftWindows 10 1507before 10.0.10240.2004810.0.10240.20048
MicrosoftWindows 10 1607before 10.0.14393.608510.0.14393.6085
MicrosoftWindows 10 1809before 10.0.17763.464510.0.17763.4645
MicrosoftWindows 10 21h2before 10.0.19041.320810.0.19041.3208
MicrosoftWindows 10 22h2before 10.0.19045.320810.0.19045.3208

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

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (microsoft.com).

Official description

Windows Error Reporting Service Elevation of Privilege Vulnerability

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

The underlying weakness: Improper Link Resolution Before File Access

The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.

How developers prevent this class of flaw

  • Follow the principle of least privilege when assigning access rights to entities in a software system. Denying access to a file can prevent an attacker from replacing that file with a link to a sensitive file. Ensure good compartmentalization in the system to provide protected areas that can be trusted.

More Improper Link Resolution Before File Access vulnerabilities (CWE-59)

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

Technical write-ups (may include proof of concept)

Recent Improper Link Resolution Before File Access vulnerabilities

Spotted an error? Tell us.