First published: Fri Dec 11 2020(Updated: )
An issue was discovered in picoTCP 1.7.0. The routine for processing the next header field (and deducing whether the IPv6 extension headers are valid) doesn't check whether the header extension length field would overflow. Therefore, if it wraps around to zero, iterating through the extension headers will not increment the current data pointer. This leads to an infinite loop and Denial-of-Service in pico_ipv6_check_headers_sequence() in pico_ipv6.c.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Altran picoTCP | <=1.7.0 | |
Multiple (open source) picoTCP-NG, Version 1.7.0 and prior | ||
Multiple (open source) picoTCP (EOL), Version 1.7.0 and prior | ||
Multiple (open source) FNET, Version 4.6.3 | ||
Multiple (open source) Nut/Net, Version 5.1 and prior |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-17444 is a vulnerability discovered in picoTCP 1.7.0 that allows for potential header extension length field overflow.
CVE-2020-17444 has a severity rating of 7.5 (high).
CVE-2020-17444 affects picoTCP 1.7.0, an Altran picoTCP software, potentially leading to header extension length field overflow.
Yes, you can refer to the following resources for more information on CVE-2020-17444: [National Vulnerability Database](https://nvd.nist.gov/vuln/detail/CVE-2020-17444), [CISA Advisory](https://us-cert.cisa.gov/ics/advisories/icsa-20-343-01), and [CERT Vulnerability Note](https://www.kb.cert.org/vuls/id/815128).
To mitigate CVE-2020-17444, it is recommended to update to a fixed version of picoTCP that addresses the header extension length field overflow issue.