CVE-2011-2716: Input Validation

Published Jul 3, 2012
·
Updated

The DHCP client (udhcpc) in BusyBox before 1.20.0 allows remote DHCP servers to execute arbitrary commands via shell metacharacters in the (1) HOSTNAME, (2) DOMAINNAME, (3) NISDOMAIN, and (4) TFTPSERVERNAME host name options.

Affected Software

92 affected components
T-Mobile Tm-ac1900=3.0.0.4.376_3169
Busybox Busybox=1.11.0
Busybox Busybox=1.12.0
Busybox Busybox=1.0.0-pre7
Busybox Busybox=1.17.1
Busybox Busybox=1.7.0
Busybox Busybox=1.12.2
Busybox Busybox=1.1.3
Busybox Busybox=1.7.1
Busybox Busybox=1.0.0-pre3
Busybox Busybox=1.4.1
Busybox Busybox=1.11.3
Busybox Busybox=1.9.2
Busybox Busybox=1.1.0
Busybox Busybox=1.0.0-pre1
Busybox Busybox=1.13.4
Busybox Busybox=1.8.2
Busybox Busybox=1.10.0
Busybox Busybox=0.60.5
Busybox Busybox=1.17.0
Busybox Busybox=1.0.0-rc3
Busybox Busybox=1.19.2
Busybox Busybox=1.16.2
Busybox Busybox=1.9.1
Busybox Busybox=1.18.5
Busybox Busybox=1.18.4
Busybox Busybox=1.8.1
Busybox Busybox=1.2.1
Busybox Busybox=1.19.0
Busybox Busybox=1.0.0-pre4
Busybox Busybox=1.1.0-pre1
Busybox Busybox=1.14.2
Busybox Busybox=1.13.0
Busybox Busybox=1.5.0
Busybox Busybox=1.13.2
Busybox Busybox=1.10.2
Busybox Busybox=1.11.1
Busybox Busybox=1.17.2
Busybox Busybox=1.2.0
Busybox Busybox=1.3.2
Busybox Busybox=1.10.4
Busybox Busybox=1.01
Busybox Busybox=1.14.1
Busybox Busybox=1.0.0-pre2
Busybox Busybox=1.7.2
Busybox Busybox=1.0.0-rc2
Busybox Busybox=1.18.1
Busybox Busybox=1.13.1
Busybox Busybox=1.14.0
Busybox Busybox=1.2.2.1
Busybox Busybox=1.0.0-pre6
Busybox Busybox=1.12.1
Busybox Busybox=1.00
Busybox Busybox=1.16.1
Busybox Busybox=1.3.1
Busybox Busybox=1.15.0
Busybox Busybox=1.11.2
Busybox Busybox=1.1.2
Busybox Busybox=1.0.0-pre10
Busybox Busybox=1.15.2
Busybox Busybox=1.0.0-pre9
Busybox Busybox=1.6.1
Busybox Busybox=1.9.0
Busybox Busybox=1.0.0-pre8
Busybox Busybox=1.17.3
Busybox Busybox=1.18.3
Busybox Busybox=1.15.1
Busybox Busybox=1.10.1
Busybox Busybox=1.12.3
Busybox Busybox=1.7.3
Busybox Busybox=1.14.3
Busybox Busybox=1.17.4
Busybox Busybox=1.0.0-rc1
Busybox Busybox=1.10.3
Busybox Busybox=1.8.0
Busybox Busybox=1.18.2
Busybox Busybox=1.4.2
Busybox Busybox<=1.19.4
Busybox Busybox=1.13.3
Busybox Busybox=1.5.1
Busybox Busybox=1.16.0
Busybox Busybox=1.19.3
Busybox Busybox=1.12.4
Busybox Busybox=1.0.0-pre5
Busybox Busybox=1.3.0
Busybox Busybox=1.6.0
Busybox Busybox=1.2.2
Busybox Busybox=1.4.0
Busybox Busybox=1.18.0
Busybox Busybox=1.1.1
Busybox Busybox=1.15.3
Busybox Busybox=1.14.4

Event History

Jul 3, 2012
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2011-2716?

CVE-2011-2716 is considered to have a moderate severity level due to the potential for remote command execution.

2

How do I fix CVE-2011-2716?

To fix CVE-2011-2716, update your BusyBox version to 1.20.0 or later, which contains the necessary patches.

3

Who is affected by CVE-2011-2716?

CVE-2011-2716 affects several versions of BusyBox prior to 1.20.0 and specific firmware implementations such as T-Mobile's TM-AC1900 router.

4

What are the potential risks of CVE-2011-2716?

The risks associated with CVE-2011-2716 include unauthorized execution of arbitrary commands on affected systems.

5

What components are primarily involved in CVE-2011-2716?

CVE-2011-2716 primarily involves the DHCP client (udhcpc) and its handling of parameters like HOST_NAME and DOMAIN_NAME.

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