Physical code execution via USB HID state corruption
Published Jun 9, 2020 · Updated Aug 4, 2024
Out-of-bounds memory access in affected FreeBSD 12.1 and 11.x releases allows physically proximate attackers to execute kernel or user-space code. The USB HID descriptor parser fails to restore its push/pop state within the same HID item, causing later item processing to use an invalid memory location. Exploitation requires physical access to a USB port and a specially crafted USB device, with execution possible in either kernel or user space.
Summary
What happened
Out-of-bounds memory access in affected FreeBSD 12.1 and 11.x releases allows physically proximate attackers to execute kernel or user-space code. The USB HID descriptor parser fails to restore its push/pop state within the same HID item, causing later item processing to use an invalid memory location. Exploitation requires physical access to a USB port and a specially crafted USB device, with execution possible in either kernel or user space.
The record
- CVE
- CVE-2020-7456
- Published
- Jun 9, 2020
- Updated
- Aug 4, 2024
- Vendor
- The FreeBSD Project
- Product
- FreeBSD
- Classifications
- CWE-119, T1200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 9, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=FreeBSD 12.1-RELEASE before p6, 11.3-RELEASE before p10, and 11.4-RC2 before p1
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