Code execution through undisclosed MSDT flaw
Published May 31, 2023 · Updated Jan 2, 2025
Code injection in Microsoft Windows Support Diagnostic Tool allows attackers to execute code after a user opens crafted content. Microsoft identifies MSDT as the affected component but has not published the vulnerable code path or operation that mishandles attacker-controlled input. Exploitation requires user interaction and runs code in the affected user's security context, permitting data access, modification, and service interruption.
Summary
What happened
Code injection in Microsoft Windows Support Diagnostic Tool allows attackers to execute code after a user opens crafted content. Microsoft identifies MSDT as the affected component but has not published the vulnerable code path or operation that mishandles attacker-controlled input. Exploitation requires user interaction and runs code in the affected user's security context, permitting data access, modification, and service interruption.
The record
- CVE
- CVE-2022-35743
- Published
- May 31, 2023
- Updated
- Jan 2, 2025
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-94, T1204
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 31, 2023CVE publishedPublication date reported by the CVE source.
- Jan 2, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0.10240.0 <10.0.10240.19387
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo