Local code execution after user interaction
Published Oct 10, 2023 · Updated Apr 14, 2025
Type confusion in Microsoft Message Queuing on affected Windows releases allows local users to execute code after user interaction. Microsoft identifies access to a resource through an incompatible type, but has not disclosed the affected MSMQ locus or the malformed input and operation that trigger the confusion. Exploitation requires low-privilege local access and user interaction, and successful execution can compromise data and interrupt the host service.
Summary
What happened
Type confusion in Microsoft Message Queuing on affected Windows releases allows local users to execute code after user interaction. Microsoft identifies access to a resource through an incompatible type, but has not disclosed the affected MSMQ locus or the malformed input and operation that trigger the confusion. Exploitation requires low-privilege local access and user interaction, and successful execution can compromise data and interrupt the host service.
The record
- CVE
- CVE-2023-36578
- Published
- Oct 10, 2023
- Updated
- Apr 14, 2025
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-843, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 10, 2023CVE publishedPublication date reported by the CVE source.
- Apr 14, 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.20232
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