Unauthorized firmware commands via unchecked oce ioctls
Published Apr 28, 2020 · Updated Aug 5, 2024
Missing authorization in the oce(4) driver in FreeBSD 11.3 and 12.1 allows local users to submit device-firmware commands. The driver-specific ioctl handlers forward firmware passthrough requests without checking the caller's kernel privilege. Exploitation requires local code execution and a system containing a network adapter driven by oce(4); the documented consequence is unauthorized firmware command submission, not kernel code execution.
Summary
What happened
Missing authorization in the oce(4) driver in FreeBSD 11.3 and 12.1 allows local users to submit device-firmware commands. The driver-specific ioctl handlers forward firmware passthrough requests without checking the caller's kernel privilege. Exploitation requires local code execution and a system containing a network adapter driven by oce(4); the documented consequence is unauthorized firmware command submission, not kernel code execution.
The record
- CVE
- CVE-2019-15876
- Published
- Apr 28, 2020
- Updated
- Aug 5, 2024
- Vendor
- The FreeBSD Project
- Product
- FreeBSD
- Classifications
- CWE-862, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 28, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=12.1-STABLE before r356089, 12.1-RELEASE before 12.1-RELEASE-p3, 11.3-STABLE before r356090, 11.3-RELEASE before 11.3-RELEASE-p7
What conditions does exploitation require?
What is affected?
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