Kernel panic via unchecked MAC key length
Published May 13, 2020 · Updated Aug 5, 2024
Denial of service in FreeBSD 12.1-STABLE before r356911 and 12.1-RELEASE before p5 allows local users to trigger a kernel panic. The cryptodev session-creation path accepts a user-supplied MAC key length and uses it directly to size a kernel buffer without validation. Exploitation requires local access to /dev/crypto and a loaded cryptodev module, which is not loaded by default, and crashes the host.
Summary
What happened
Denial of service in FreeBSD 12.1-STABLE before r356911 and 12.1-RELEASE before p5 allows local users to trigger a kernel panic. The cryptodev session-creation path accepts a user-supplied MAC key length and uses it directly to size a kernel buffer without validation. Exploitation requires local access to /dev/crypto and a loaded cryptodev module, which is not loaded by default, and crashes the host.
The record
- CVE
- CVE-2019-15880
- Published
- May 13, 2020
- Updated
- Aug 5, 2024
- Vendor
- The FreeBSD Project
- Product
- FreeBSD
- Classifications
- CWE-119, CWE-20, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 13, 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=FreeBSD 12.1-RELEASE before p5
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.
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