Skip to main content

CVE-2021-42374: CWE-125 in busybox busybox

Medium
VulnerabilityCVE-2021-42374cvecve-2021-42374cwe-125
Published: Mon Nov 15 2021 (11/15/2021, 00:00:00 UTC)
Source: CVE
Vendor/Project: busybox
Product: busybox

Description

An out-of-bounds heap read in Busybox's unlzma applet leads to information leak and denial of service when crafted LZMA-compressed input is decompressed. This can be triggered by any applet/format that

AI-Powered Analysis

AILast updated: 07/06/2025, 22:41:49 UTC

Technical Analysis

CVE-2021-42374 is a medium-severity vulnerability identified in BusyBox, specifically affecting the unlzma applet responsible for decompressing LZMA-compressed data. The vulnerability is classified as CWE-125, indicating an out-of-bounds heap read condition. This flaw arises when the unlzma applet processes crafted LZMA-compressed input, leading to an out-of-bounds read on the heap memory. The consequence of this vulnerability includes potential information leakage and denial of service (DoS). The information leak occurs because the out-of-bounds read may expose sensitive memory contents, while the DoS results from the application crashing or becoming unresponsive due to memory access violations. The vulnerability can be triggered by any applet or format within BusyBox that utilizes the unlzma decompression functionality. Exploitation requires local access (AV:L) with low privileges (PR:L), no user interaction (UI:N), and is considered to have high attack complexity (AC:H). The scope is unchanged (S:U), impacting confidentiality (C:L) and availability (A:H), but not integrity (I:N). There are no known exploits in the wild, and the affected versions are unspecified, indicating that users should verify their BusyBox versions and monitor for patches. BusyBox is widely used in embedded systems, routers, IoT devices, and lightweight Linux distributions, making this vulnerability relevant in environments where BusyBox is deployed. The lack of a patch link suggests that remediation may require manual updates or vendor-specific fixes. Overall, this vulnerability poses a risk primarily through denial of service and limited information disclosure via crafted LZMA inputs processed by BusyBox's unlzma applet.

Potential Impact

For European organizations, the impact of CVE-2021-42374 depends largely on the deployment of BusyBox within their infrastructure. Many embedded devices, network appliances, and IoT systems in industrial, telecommunications, and enterprise environments use BusyBox due to its small footprint. A successful exploitation could lead to denial of service on critical devices, potentially disrupting network operations, industrial control systems, or other embedded applications. The information leak aspect, while limited, could expose sensitive memory contents, which might include cryptographic keys or configuration data, depending on the device context. This could facilitate further attacks or data breaches. Given the high attack complexity and requirement for local access with low privileges, remote exploitation is less likely without prior compromise. However, in scenarios where attackers have foothold or physical access, this vulnerability could be leveraged to escalate impact. European organizations with extensive IoT deployments or critical infrastructure using BusyBox should be particularly vigilant. Disruptions to availability in sectors such as manufacturing, energy, or telecommunications could have cascading effects on operational continuity and service delivery.

Mitigation Recommendations

To mitigate CVE-2021-42374, European organizations should: 1) Inventory all devices and systems running BusyBox, especially those utilizing the unlzma applet or LZMA decompression features. 2) Apply vendor-supplied patches or updates as soon as they become available; if no official patch exists, consider upgrading BusyBox to a version where this vulnerability is fixed. 3) Restrict local access to devices running BusyBox to trusted personnel only, employing strong access controls and network segmentation to limit exposure. 4) Monitor logs and system behavior for signs of abnormal crashes or memory errors related to unlzma or decompression operations. 5) For embedded and IoT devices where patching is challenging, consider compensating controls such as disabling unlzma functionality if not required, or deploying network-level protections to prevent delivery of crafted LZMA inputs. 6) Conduct security assessments and penetration testing focusing on BusyBox components to identify potential exploitation paths. 7) Educate operational technology and IT teams about this vulnerability to ensure timely detection and response. These measures go beyond generic advice by emphasizing asset inventory, access restriction, and compensating controls tailored to embedded environments common in European sectors.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
JFROG
Date Reserved
2021-10-14T00:00:00.000Z
Cisa Enriched
true
Cvss Version
3.1
State
PUBLISHED

Threat ID: 682d981ec4522896dcbdbbfe

Added to database: 5/21/2025, 9:08:46 AM

Last enriched: 7/6/2025, 10:41:49 PM

Last updated: 8/16/2025, 7:15:47 PM

Views: 10

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats