An issue was discovered in FNET through 4.6.4. The code for IPv6 fragment reassembly tries to access a previous fragment starting from a network incoming fragment that still doesn't have a reference to the previous one (which supposedly resides in the reassembly list). When faced with an incoming fragment that belongs to a non-empty fragment list, IPv6 reassembly must check that there are no empty holes between the fragments: this leads to an uninitialized pointer dereference in _fnet_ip6_reassembly in fnet_ip6.c, and causes Denial-of-Service.
References
Link | Resource |
---|---|
http://fnet.sourceforge.net/manual/fnet_history.html | Release Notes Third Party Advisory |
https://us-cert.cisa.gov/ics/advisories/icsa-20-343-01 | Third Party Advisory US Government Resource |
https://www.kb.cert.org/vuls/id/815128 | Third Party Advisory US Government Resource |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: mitre
Published: 2020-12-11T22:39:54
Updated: 2020-12-11T22:39:54
Reserved: 2020-08-10T00:00:00
Link: CVE-2020-17469
JSON object: View
NVD Information
Status : Analyzed
Published: 2020-12-11T23:15:13.683
Modified: 2023-10-12T18:31:10.153
Link: CVE-2020-17469
JSON object: View
Redhat Information
No data.
CWE