System panic via unbounded neighbor-cache allocation
Published Feb 20, 2020 · Updated Aug 6, 2024
Uncontrolled resource consumption in FreeBSD and NetBSD IPv6 stacks through 2012 allows remote attackers to trigger a system panic. Each Neighbor Solicitation carrying a source link-layer address creates a neighbor-cache entry without an enforced entry limit. The flood must reach an IPv6 link, and entries arriving faster than pruning consume kernel memory until the host panics.
Summary
What happened
Uncontrolled resource consumption in FreeBSD and NetBSD IPv6 stacks through 2012 allows remote attackers to trigger a system panic. Each Neighbor Solicitation carrying a source link-layer address creates a neighbor-cache entry without an enforced entry limit. The flood must reach an IPv6 link, and entries arriving faster than pruning consume kernel memory until the host panics.
The record
- CVE
- CVE-2012-5363
- Published
- Feb 20, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 20, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- THC-IPv6 flood_solicitate6functional · unverified
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