RHSA-2012:0308: Low: busybox security and bug fix update

Published Feb 21, 2012
·
Updated

BusyBox provides a single binary that includes versions of a large numberof system commands, including a shell. This can be very useful forrecovering from certain types of system failures, particularly thoseinvolving broken shared libraries.A buffer underflow flaw was found in the way the uncompress utility ofBusyBox expanded certain archive files compressed using Lempel-Zivcompression. If a user were tricked into expanding a specially-craftedarchive file with uncompress, it could cause BusyBox to crash or,potentially, execute arbitrary code with the privileges of the user runningBusyBox. (CVE-2006-1168)The BusyBox DHCP client, udhcpc, did not sufficiently sanitize certainoptions provided in DHCP server replies, such as the client hostname. Amalicious DHCP server could send such an option with a specially-craftedvalue to a DHCP client. If this option's value was saved on the clientsystem, and then later insecurely evaluated by a process that assumes theoption is trusted, it could lead to arbitrary code execution with theprivileges of that process. Note: udhcpc is not used on Red Hat EnterpriseLinux by default, and no DHCP client script is provided with the busyboxpackages. (CVE-2011-2716)This update also fixes the following bugs: Prior to this update, the cp command wrongly returned the exit code 0 to indicate success if a device ran out of space while attempting to copyfiles of more than 4 gigabytes. This update modifies BusyBox, so that insuch situations, the exit code 1 is returned. Now, the cp command showscorrectly whether a process failed. (BZ#689659) Prior to this update, the findfs command failed to check all existing block devices on a system with thousands of block device nodes in "/dev/".This update modifies BusyBox so that findfs checks all block devices evenin this case. (BZ#756723)All users of busybox are advised to upgrade to these updated packages,which correct these issues.

Affected Software

4 affected componentsFixes available
redhat/busybox<1.2.0-13.el5
1.2.0-13.el5
redhat/busybox<1.2.0-13.el5
1.2.0-13.el5
redhat/busybox-anaconda<1.2.0-13.el5
1.2.0-13.el5
redhat/busybox-anaconda<1.2.0-13.el5
1.2.0-13.el5

Remediation

Event History

Feb 21, 2012
Advisory Published
via Red Hat·12:00 AM
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 RHSA-2012:0308?

RHSA-2012:0308 is classified as a moderate severity vulnerability.

2

How do I fix RHSA-2012:0308?

To fix RHSA-2012:0308, update BusyBox to version 1.2.0-13.el5 or later.

3

What vulnerability does RHSA-2012:0308 address?

RHSA-2012:0308 addresses a buffer underflow flaw in BusyBox.

4

Which versions of BusyBox are affected by RHSA-2012:0308?

Versions of BusyBox prior to 1.2.0-13.el5 are affected by RHSA-2012:0308.

5

Is there a workaround for RHSA-2012:0308?

No specific workaround is provided for RHSA-2012:0308, and updating is recommended.

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