First published: Wed Aug 03 2016(Updated: )
The busybox NTP implementation doesn't check the NTP mode of packets received on the server port and responds to any packet with the right size. This includes responses from another NTP server. An attacker can send a packet with a spoofed source address in order to create an infinite loop of responses between two busybox NTP servers. Adding more packets to the loop increases the traffic between the servers until one of them has a fully loaded CPU and/or network. It seems this bug was actually inherited from openntpd, on which the busybox implementation was based on. In openntpd it was fixed in: <a href="https://github.com/openntpd-portable/openntpd-openbsd/commit/28a2f904aafbf4c209fe6fa04ffb9308740fd78a">https://github.com/openntpd-portable/openntpd-openbsd/commit/28a2f904aafbf4c209fe6fa04ffb9308740fd78a</a> Busybox upstream patch: <a href="https://git.busybox.net/busybox/commit/?id=150dc7a2b483b8338a3e185c478b4b23ee884e71">https://git.busybox.net/busybox/commit/?id=150dc7a2b483b8338a3e185c478b4b23ee884e71</a>
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Busybox Busybox | <1.25.1 | |
Advantech Spectre RT ERT351 firmware Versions 5.1.3 and prior |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.