Physical code execution via expired pointer dereference
Published Dec 5, 2023 · Updated Nov 27, 2024
Expired-pointer dereferences in Eclipse ThreadX USBX before 6.3.0 allow physically proximate attackers to execute arbitrary code. The host hub-entry and EHCI isochronous-endpoint creation paths dereference objects after their backing memory has been freed; linked host-class code includes GSER and HID. Exploitation requires a crafted USB device to reach an affected embedded USB host, with unauthorized code execution and resulting confidentiality and integrity loss.
Summary
What happened
Expired-pointer dereferences in Eclipse ThreadX USBX before 6.3.0 allow physically proximate attackers to execute arbitrary code. The host hub-entry and EHCI isochronous-endpoint creation paths dereference objects after their backing memory has been freed; linked host-class code includes GSER and HID. Exploitation requires a crafted USB device to reach an affected embedded USB host, with unauthorized code execution and resulting confidentiality and integrity loss.
The record
- CVE
- CVE-2023-48698
- Published
- Dec 5, 2023
- Updated
- Nov 27, 2024
- Vendor
- The Eclipse Foundation
- Product
- Eclipse ThreadX USBX
- Classifications
- CWE-825, CWE-754, T1203
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 5, 2023CVE publishedPublication date reported by the CVE source.
- Nov 27, 2024Record 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=< 6.3.0
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