Privilege escalation via mishandled Unicode source
Published Feb 16, 2023 · Updated Jan 27, 2025
Improper Unicode handling in Intel C++ Compiler Classic before 2021.6 allows remote attackers to escalate privileges through compiled source code. Release 2021.6 adds Unicode-security source checking, but Intel has not disclosed which Unicode sequences earlier releases mishandle or how compilation changes. Exploitation requires user interaction with network-delivered source code, and the published consequence is privilege escalation across a security boundary.
Summary
What happened
Improper Unicode handling in Intel C++ Compiler Classic before 2021.6 allows remote attackers to escalate privileges through compiled source code. Release 2021.6 adds Unicode-security source checking, but Intel has not disclosed which Unicode sequences earlier releases mishandle or how compilation changes. Exploitation requires user interaction with network-delivered source code, and the published consequence is privilege escalation across a security boundary.
The record
- CVE
- CVE-2022-25987
- Published
- Feb 16, 2023
- Updated
- Jan 27, 2025
- Vendor
- Topcon Positioning Systems, Inc.
- Product
- Intel C++ Compiler Classic
- Classifications
- T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 16, 2023CVE publishedPublication date reported by the CVE source.
- Jan 27, 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=before version 2021.6
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