Kernel panic via SCTP-AUTH key update use-after-free
Published May 13, 2020 · Updated Aug 5, 2024
Use-after-free in the FreeBSD 11.3 kernel before 11.3-RELEASE-p9 allows local users to trigger a kernel panic via SCTP-AUTH key updates. The SCTP layer fails to validate a shared-key update sequence before an association is closed, leaving kernel code to access freed state. Any unprivileged local account that can use the SCTP socket API can interrupt the host by causing the kernel panic.
Summary
What happened
Use-after-free in the FreeBSD 11.3 kernel before 11.3-RELEASE-p9 allows local users to trigger a kernel panic via SCTP-AUTH key updates. The SCTP layer fails to validate a shared-key update sequence before an association is closed, leaving kernel code to access freed state. Any unprivileged local account that can use the SCTP socket API can interrupt the host by causing the kernel panic.
The record
- CVE
- CVE-2019-15878
- Published
- May 13, 2020
- Updated
- Aug 5, 2024
- Vendor
- The FreeBSD Project
- Product
- FreeBSD
- Classifications
- CWE-416, T1499
- 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 11.3-RELEASE before p9
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