First published: Tue Oct 10 2023(Updated: )
An issue was discovered in Ethernut Nut/OS 5.1. The code that generates Initial Sequence Numbers (ISNs) for TCP connections derives the ISN from an insufficiently random source. As a result, an attacker may be able to determine the ISN of current and future TCP connections and either hijack existing ones or spoof future ones. While the ISN generator seems to adhere to RFC 793 (where a global 32-bit counter is incremented roughly every 4 microseconds), proper ISN generation should aim to follow at least the specifications outlined in RFC 6528.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Ethernut Nut\/os | =5.1 | |
Multiple Nut/Net, Version 5.1 and prior | ||
Multiple CycloneTCP, Version 1.9.6 and prior | ||
Multiple NDKTCPIP, Version 2.25 and prior | ||
Multiple FNET, Version 4.6.3 | ||
Multiple uIP-Contiki-OS (end-of-life [EOL]), Version 3.0 and prior | ||
Multiple uC/TCP-IP (EOL), Version 3.6.0 and prior | ||
Multiple uIP-Contiki-NG, Version 4.5 and prior | ||
Multiple uIP (EOL), Version 1.0 and prior | ||
Multiple picoTCP-NG, Version 1.7.0 and prior | ||
Multiple picoTCP (EOL), Version 1.7.0 and prior | ||
Multiple MPLAB Net, Version 3.6.1 and prior | ||
Multiple Nucleus NET, All versions prior to Version 5.2 | ||
Multiple Nucleus ReadyStart for ARM, MIPS, and PPC, All versions prior to Version 2012.12 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.