Privileged heap disclosure via non-atomic registry commits
Published Jun 13, 2023 · Updated Jan 1, 2025
Windows Kernel information disclosure allows local users to read privileged-process heap memory through crafted registry transactions. The Configuration Manager can partially commit a KTM registry transaction after an out-of-memory error, falsely report success, and leave registry changes non-atomic. Exploitation requires low-privileged local code to coordinate the transaction failure with a privileged process running as another user.
Summary
What happened
Windows Kernel information disclosure allows local users to read privileged-process heap memory through crafted registry transactions. The Configuration Manager can partially commit a KTM registry transaction after an out-of-memory error, falsely report success, and leave registry changes non-atomic. Exploitation requires low-privileged local code to coordinate the transaction failure with a privileged process running as another user.
The record
- CVE
- CVE-2023-32019
- Published
- Jun 13, 2023
- Updated
- Jan 1, 2025
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-668
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 13, 2023CVE publishedPublication date reported by the CVE source.
- Jan 1, 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.17763.0 <10.0.17763.4499
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