Security readout for executives and security teams
Plain-English summary
This Windows flaw can let malicious content use the Microsoft Support Diagnostic Tool to run code when handled by an application such as Word. The code inherits that application's privileges, potentially enabling program installation, data theft or alteration, deletion, or account creation within the user's rights. User interaction is required, but CISA lists the vulnerability as known exploited.
Executive priority
Urgent. Confirm coverage and implement Microsoft's applicable guidance promptly, prioritizing systems where untrusted documents can reach interactive users. KEV status means this is not a theoretical risk, while high-impact code execution can cause material operational and data consequences. Report remediation gaps and exceptions to leadership until closed.
Technical view
MSDT can be invoked through its URL protocol from a calling application such as Word, leading to arbitrary code execution under that application's privileges. Its CVSS 3.1 score is 7.8: low complexity, no prior privileges, user interaction required, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is possible on unremediated assets running the listed Windows 7, 8.1, 10, or 11 21H2 releases, plus listed Windows Server 2008 R2, 2012, 2016, 2019, 20H2, and 2022 releases. Risk is greatest where users open untrusted content in applications such as Word. The bundle cannot establish any organization's actual exposure.
Exploitation context
CISA's Known Exploited Vulnerabilities catalog supports known real-world exploitation. The CVSS vector marks exploit-code maturity as proof-of-concept. The bundle does not identify campaigns, victims, exploitation volume, or current activity levels, so those details remain unknown.
Researcher notes
The vector is CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C. Execution remains within the calling application's privilege context. The supplied record identifies no CWE, specific security-update identifiers, campaign details, or indicators of compromise; consult Microsoft for exact release-specific remediation.
Mitigation direction
- Consult Microsoft's CVE guidance and apply the official remediation applicable to each affected Windows release.
- Prioritize systems whose users routinely open external Word documents, email attachments, or downloaded files.
- Use existing email and endpoint controls to restrict untrusted documents until remediation is verified.
Validation and detection
- Inventory the specifically listed Windows releases and compare each asset with Microsoft's applicability guidance.
- Confirm Microsoft's applicable remediation is implemented on every exposed asset.
- Review endpoint telemetry for unexpected MSDT launches associated with Word or other document-handling applications.
- Use non-exploit vulnerability scanning or configuration checks to verify remediation coverage.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-30190 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C1.85.9microsoftVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- Added to KEVCISA-ADP
CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Microsoft Windows Support Diagnostic Tool (MSDT) Remote Code Execution VulnerabilityCVE reference, microsoft · vendor-advisory
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2022-30190CVE reference, CVE · x_refsource_MISC, x_transferred
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-30190CVE reference, CISA-ADP · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.