Authenticated heap-memory disclosure via untrusted pointer dereference
Published Jan 9, 2024 · Updated May 3, 2025
Untrusted pointer dereference in Microsoft Message Queuing on affected Windows releases allows remote authenticated users to read heap memory. Microsoft identifies the weakness class but has not published the affected function, packet field, or incorrect pointer operation. Exploitation requires low-privileged authentication and network access to MSMQ; the reported consequence is confidentiality loss without data modification or service interruption.
Summary
What happened
Untrusted pointer dereference in Microsoft Message Queuing on affected Windows releases allows remote authenticated users to read heap memory. Microsoft identifies the weakness class but has not published the affected function, packet field, or incorrect pointer operation. Exploitation requires low-privileged authentication and network access to MSMQ; the reported consequence is confidentiality loss without data modification or service interruption.
The record
- CVE
- CVE-2024-20664
- Published
- Jan 9, 2024
- Updated
- May 3, 2025
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-822, T1210
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 9, 2024CVE publishedPublication date reported by the CVE source.
- May 3, 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.20402
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