Physical privilege escalation via unchecked return value
Published Aug 14, 2024 · Updated Nov 3, 2025
Unchecked return-value handling in Intel CSME firmware allows physically proximate attackers to escalate privileges without authentication. The firmware fails to check a function's return value, but Intel has not disclosed the function, failure path, or affected subsystem. Physical access to an affected chipset is required; successful exploitation alters CSME integrity and can expose limited data in a subsequent component.
Summary
What happened
Unchecked return-value handling in Intel CSME firmware allows physically proximate attackers to escalate privileges without authentication. The firmware fails to check a function's return value, but Intel has not disclosed the function, failure path, or affected subsystem. Physical access to an affected chipset is required; successful exploitation alters CSME integrity and can expose limited data in a subsequent component.
The record
- CVE
- CVE-2023-40067
- Published
- Aug 14, 2024
- Updated
- Nov 3, 2025
- Vendor
- Topcon Positioning Systems, Inc.
- Product
- Intel Converged Security and Manageability Engine
- Classifications
- CWE-252, T1068
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 14, 2024CVE publishedPublication date reported by the CVE source.
- Nov 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=See references
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