REDHAT-BUG-1363710: Medium severity BusyBox BusyBox vulnerability

Published Aug 3, 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:

https://github.com/openntpd-portable/openntpd-openbsd/commit/28a2f904aafbf4c209fe6fa04ffb9308740fd78a

Busybox upstream patch:

https://git.busybox.net/busybox/commit/?id=150dc7a2b483b8338a3e185c478b4b23ee884e71

Affected Software

2 affected components
BusyBox BusyBox
OpenBSD OpenNTPD

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade BusyBox to a version that resolves this vulnerability.

    Patch 150dc7a2b483b8338a3e185c478b4b23ee884e71
  2. Upgrade

    Upgrade OpenNTPD to a version that resolves this vulnerability.

    Patch 28a2f904aafbf4c209fe6fa04ffb9308740fd78a

Event History

Aug 3, 2016
Data Sourced
via Red Hat·12:11 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of REDHAT-BUG-1363710?

The severity of REDHAT-BUG-1363710 is considered high due to the potential for an attacker to create an infinite loop of responses.

2

How do I fix REDHAT-BUG-1363710?

To fix REDHAT-BUG-1363710, you need to update to the patched versions of BusyBox and OpenNTPD that address the vulnerability.

3

What systems are affected by REDHAT-BUG-1363710?

Affected systems include BusyBox and OpenNTPD implementations that do not properly verify the mode of NTP packets.

4

What is the exploit technique used in REDHAT-BUG-1363710?

The exploit technique involves sending a NTP packet with a spoofed source address to trigger a response loop.

5

Is there any known workaround for REDHAT-BUG-1363710?

A known workaround for REDHAT-BUG-1363710 is to configure firewall rules to restrict NTP traffic from untrusted sources.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203