Remote kernel panic via stale mbuf access
Published Apr 28, 2020 · Updated Aug 5, 2024
Use-after-free in ipfw in FreeBSD 11.3 and 12.1 allows remote attackers to trigger a kernel panic via crafted TCP packets. When tcpoptions or tcpmss rules inspect a noncontiguous TCP header, ipfw's packet pull-up path can free an mbuf while later rule processing retains and dereferences stale packet pointers. Exposure requires ipfw rules using the tcpoptions or tcpmss keywords; successful exploitation interrupts the host by panicking its kernel.
Summary
What happened
Use-after-free in ipfw in FreeBSD 11.3 and 12.1 allows remote attackers to trigger a kernel panic via crafted TCP packets. When tcpoptions or tcpmss rules inspect a noncontiguous TCP header, ipfw's packet pull-up path can free an mbuf while later rule processing retains and dereferences stale packet pointers. Exposure requires ipfw rules using the tcpoptions or tcpmss keywords; successful exploitation interrupts the host by panicking its kernel.
The record
- CVE
- CVE-2019-15874
- Published
- Apr 28, 2020
- Updated
- Aug 5, 2024
- Vendor
- The FreeBSD Project
- Product
- FreeBSD
- Classifications
- CWE-416, CWE-20, T1499
- Attack vector
- network
- Privileges
- unauthenticated
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=FreeBSD 12.1-STABLE before r356035, 12.1-RELEASE before 12.1-RELEASE-p4, 11.3-STABLE before r356036, 11.3-RELEASE before 11.3-RELEASE-p8
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