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

Microsoft Windows Support Diagnostic Tool (MSDT) Remote Code Execution

Published Updated By the CyberSecBulletin desk

CVE-2022-30190 is a high-severity 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 unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 10.0.17763.3046 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 June 14, 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.3046 or a later version.
  2. Update Windows Server 2019 to 10.0.17763.3046 or a later version.
  3. Update Windows Server 2019 (Server Core installation) to 10.0.17763.3046 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.
  6. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

VendorProductAffected versionsFixed in
MicrosoftWindows 10 Version 180910.0.17763.0 up to, but not including, 10.0.17763.3046; 10.0.0 up to, but not including, 10.0.17763.304610.0.17763.3046
MicrosoftWindows Server 201910.0.17763.0 up to, but not including, 10.0.17763.304610.0.17763.3046
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0 up to, but not including, 10.0.17763.304610.0.17763.3046
MicrosoftWindows 10 Version 21H110.0.0 up to, but not including, 10.0.19043.176610.0.19043.1766
MicrosoftWindows Server 202210.0.20348.0 up to, but not including, 10.0.20348.77010.0.20348.770
MicrosoftWindows 10 Version 20H210.0.0 up to, but not including, 10.0.19042.176610.0.19042.1766
MicrosoftWindows Server version 20H210.0.0 up to, but not including, 10.0.19042.176610.0.19042.1766
MicrosoftWindows 11 version 21H210.0.0 up to, but not including, 10.0.22000.73910.0.22000.739
MicrosoftWindows 10 Version 21H210.0.19043.0 up to, but not including, 10.0.19044.176610.0.19044.1766
MicrosoftWindows 10 Version 150710.0.10240.0 up to, but not including, 10.0.10240.1932510.0.10240.19325
MicrosoftWindows 10 Version 160710.0.14393.0 up to, but not including, 10.0.14393.519210.0.14393.5192
MicrosoftWindows Server 201610.0.14393.0 up to, but not including, 10.0.14393.519210.0.14393.5192
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0 up to, but not including, 10.0.14393.519210.0.14393.5192
MicrosoftWindows 76.1.0 up to, but not including, 6.1.7601.259846.1.7601.25984
MicrosoftWindows 7 Service Pack 16.1.0 up to, but not including, 6.1.7601.259846.1.7601.25984
MicrosoftWindows 8.16.3.0 up to, but not including, 6.3.9600.204026.3.9600.20402
MicrosoftWindows Server 2008 R2 Service Pack 16.1.7601.0 up to, but not including, 6.1.7601.259846.1.7601.25984
MicrosoftWindows Server 2008 R2 Service Pack 1 (Server Core installation)6.1.7601.0 up to, but not including, 6.1.7601.259846.1.7601.25984
MicrosoftWindows Server 20126.2.9200.0 up to, but not including, 6.2.9200.237366.2.9200.23736
MicrosoftWindows Server 2012 (Server Core installation)6.2.9200.0 up to, but not including, 6.2.9200.237366.2.9200.23736
MicrosoftWindows Server 2012 R26.3.9600.0 up to, but not including, 6.3.9600.204026.3.9600.20402
MicrosoftWindows Server 2012 R2 (Server Core installation)6.3.9600.0 up to, but not including, 6.3.9600.204026.3.9600.20402
MicrosoftWindows 10 1507before 10.0.10240.1932510.0.10240.19325
MicrosoftWindows 10 1607before 10.0.14393.519210.0.14393.5192
MicrosoftWindows 10 1809before 10.0.17763.304610.0.17763.3046

Version data comes from the organisation that assigned the CVE; 7 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
NoneNo account or login is needed.
User interaction
RequiredA user must take an action such as opening a file or link.
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:N/UI:R/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.8HighCNA (microsoft.com)
CVSS 3.17.8HighNVD
CVSS 2.09.3HighNVD

Official description

A remote code execution vulnerability exists when MSDT is called using the URL protocol from a calling application such as Word. An attacker who successfully exploits this vulnerability can run arbitrary code with the privileges of the calling application. The attacker can then install programs, view, change, or delete data, or create new accounts in the context allowed by the user’s rights. Please see the MSRC Blog Entry for important information about steps you can take to protect your system from this vulnerability.

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

Timeline

  1. CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
  2. CVE record published.
  3. Added to CISA's Known Exploited Vulnerabilities catalogue.
  4. Deadline for US federal agencies to remediate, set by CISA.
  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)

Spotted an error? Tell us.