Local memory disclosure via buffer over-read
Published Apr 9, 2024 · Updated May 3, 2025
Buffer over-read in Windows Remote Access Connection Manager allows local users to disclose memory on affected Windows releases. Microsoft identifies the component and buffer over-read class but has not published the affected function or the input whose length is mishandled. Local low-privilege access is required, and the reported consequence is confined to reading process memory.
Summary
What happened
Buffer over-read in Windows Remote Access Connection Manager allows local users to disclose memory on affected Windows releases. Microsoft identifies the component and buffer over-read class but has not published the affected function or the input whose length is mishandled. Local low-privilege access is required, and the reported consequence is confined to reading process memory.
The record
- CVE
- CVE-2024-26255
- Published
- Apr 9, 2024
- Updated
- May 3, 2025
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-126, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 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.17763.0 <10.0.17763.5696
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.
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