Authenticated code execution via crafted XPS file
Published Apr 11, 2023 · Updated Feb 28, 2025
Type confusion in Microsoft PostScript and PCL6 Class Printer Driver allows remote authenticated users to execute code via a crafted XPS file. Microsoft identifies type confusion but has not disclosed the affected routine, the mis-typed XPS object, or the specific invalid access. Exploitation requires a normal-privilege authenticated user to submit the modified XPS file to a shared printer, where successful processing runs attacker-controlled code.
Summary
What happened
Type confusion in Microsoft PostScript and PCL6 Class Printer Driver allows remote authenticated users to execute code via a crafted XPS file. Microsoft identifies type confusion but has not disclosed the affected routine, the mis-typed XPS object, or the specific invalid access. Exploitation requires a normal-privilege authenticated user to submit the modified XPS file to a shared printer, where successful processing runs attacker-controlled code.
The record
- CVE
- CVE-2023-24885
- Published
- Apr 11, 2023
- Updated
- Feb 28, 2025
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-843, T1210
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 11, 2023CVE publishedPublication date reported by the CVE source.
- Feb 28, 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.19869
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