Local privilege escalation via improperly locked memory
Published Apr 11, 2023 · Updated Jan 23, 2025
Improperly locked memory in Microsoft Windows Clip Service allows local users to elevate privileges on affected Windows builds. Microsoft classifies the flaw as sensitive data storage in improperly locked memory but has not disclosed the code locus or incorrect operation. Low-privilege local access and a high-complexity exploitation path are required; Microsoft does not identify the resulting privilege level.
Summary
What happened
Improperly locked memory in Microsoft Windows Clip Service allows local users to elevate privileges on affected Windows builds. Microsoft classifies the flaw as sensitive data storage in improperly locked memory but has not disclosed the code locus or incorrect operation. Low-privilege local access and a high-complexity exploitation path are required; Microsoft does not identify the resulting privilege level.
The record
- CVE
- CVE-2023-28273
- Published
- Apr 11, 2023
- Updated
- Jan 23, 2025
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-591, CWE-362, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 11, 2023CVE publishedPublication date reported by the CVE source.
- Jan 23, 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.4252
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