CVE-2016-6301
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 |
|---|---|---|
| Ubuntu BusyBox Static | <1.25.1 | |
| Advantech Spectre Rt Ert351 Firmware |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://github.com/openntpd-portable/openntpd-openbsd/commit/28a2f904aafbf4c209fe6fa04ffb9308740fd78a
- https://git.busybox.net/busybox/commit/?id=150dc7a2b483b8338a3e185c478b4b23ee884e71
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1363711
- https://bugzilla.redhat.com/show_bug.cgi?id=1363710
- http://packetstormsecurity.com/files/153278/WAGO-852-Industrial-Managed-Switch-Series-Code-Execution-Hardcoded-Credentials.html
- http://packetstormsecurity.com/files/154361/Cisco-Device-Hardcoded-Credentials-GNU-glibc-BusyBox.html
- http://seclists.org/fulldisclosure/2019/Jun/18
- http://seclists.org/fulldisclosure/2019/Sep/7
- http://seclists.org/fulldisclosure/2020/Aug/20
- http://seclists.org/fulldisclosure/2020/Mar/15
- http://www.openwall.com/lists/oss-security/2016/08/03/7
- http://www.securityfocus.com/bid/92277
- https://seclists.org/bugtraq/2019/Jun/14
- https://seclists.org/bugtraq/2019/Sep/7
- https://security.gentoo.org/glsa/201701-05
- https://www.cisa.gov/news-events/ics-advisories/icsa-21-054-03 (Advisory)
Frequently Asked Questions
What is the severity of CVE-2016-6301?
CVE-2016-6301 is classified as a high-severity vulnerability due to its potential for creating denial-of-service conditions.
How do I fix CVE-2016-6301?
To fix CVE-2016-6301, upgrade to BusyBox version 1.25.1 or later, or apply patches from your vendor.
What kind of systems are affected by CVE-2016-6301?
CVE-2016-6301 affects BusyBox implementations as well as Advantech Spectre RT ERT351 firmware Versions 5.1.3 and prior.
What type of attack is associated with CVE-2016-6301?
CVE-2016-6301 is associated with NTP reflection attacks where an attacker can spoof source addresses to create an amplification effect.
Is CVE-2016-6301 still a concern in current systems?
Yes, CVE-2016-6301 remains a concern if systems using vulnerable versions of BusyBox or Advantech firmware are not updated.
- agent/type
- agent/first-publish-date
- agent/author
- agent/weakness
- agent/references
- agent/severity
- agent/remedy
- agent/description
- collector/mitre-cve
- source/MITRE
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2016-6301
- agent/last-modified-date
- agent/event
- agent/trending
- agent/source
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/tags
- agent/softwarecombine
- collector/ics-cert-advisory
- source/ICS
- alias/CVE-2015-9261
- agent/software-canonical-lookup
- vendor/busybox
- canonical/ubuntu busybox static
- vendor/advantech
- canonical/advantech spectre rt ert351 firmware