Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-57257: CWE-674 Uncontrolled Recursion in denx U-Boot

0
Low
VulnerabilityCVE-2024-57257cvecve-2024-57257cwe-674
Published: Tue Feb 18 2025 (02/18/2025, 00:00:00 UTC)
Source: CVE Database V5
Vendor/Project: denx
Product: U-Boot

Description

A stack consumption issue in sqfs_size in Das U-Boot before 2025.01-rc1 occurs via a crafted squashfs filesystem with deep symlink nesting.

AI-Powered Analysis

AILast updated: 11/03/2025, 20:05:55 UTC

Technical Analysis

CVE-2024-57257 identifies a stack consumption vulnerability in the sqfs_size function of the denx U-Boot bootloader prior to version 2025.01-rc1. The issue stems from uncontrolled recursion caused by processing a crafted squashfs filesystem image that contains deeply nested symbolic links. When U-Boot attempts to parse such a filesystem, the recursive calls to resolve symlinks can consume excessive stack space, potentially leading to a stack overflow or exhaustion. This condition may cause the bootloader to crash or behave unpredictably, resulting in a denial of service during the boot process. The vulnerability is classified under CWE-674 (Uncontrolled Recursion), which highlights the risk of recursive function calls without proper termination conditions or depth limits. Exploitation requires an attacker to supply a malicious squashfs image to the device, which typically implies local or physical access or control over the firmware update process. The CVSS v3.1 base score is 2.0, reflecting low severity due to the high attack complexity, lack of privileges required, no user interaction, and limited impact confined to availability. No known public exploits or active exploitation have been reported. The vulnerability affects all versions of U-Boot before 2025.01-rc1, a widely used open-source bootloader in embedded systems, IoT devices, and industrial equipment. Since U-Boot is often used in critical infrastructure and embedded environments, this vulnerability could disrupt device availability if exploited, but it does not compromise confidentiality or integrity of the system. No patches were linked at the time of reporting, but upgrading to the fixed version is the recommended remediation.

Potential Impact

For European organizations, the primary impact of CVE-2024-57257 is a potential denial of service during device boot due to stack exhaustion caused by maliciously crafted squashfs images. This could disrupt operations in environments relying on embedded devices or industrial control systems that use U-Boot as their bootloader. While the vulnerability does not allow data theft or unauthorized code execution, availability interruptions could affect critical infrastructure, manufacturing lines, or IoT deployments. The requirement for local or physical access to supply the malicious filesystem limits remote exploitation risks, but insider threats or supply chain attacks could leverage this vulnerability. Organizations with extensive embedded device fleets, such as automotive manufacturers, telecommunications providers, and industrial automation companies, may face operational disruptions if devices are not updated. However, the low CVSS score and absence of known exploits reduce the immediate threat level. Still, failure to address this vulnerability could increase risk exposure in environments where device uptime is critical.

Mitigation Recommendations

To mitigate CVE-2024-57257, European organizations should: 1) Monitor for and apply updates to U-Boot, specifically upgrading to version 2025.01-rc1 or later once officially released, as this version contains the fix for the uncontrolled recursion issue. 2) Implement strict validation and integrity checks on squashfs filesystem images before deployment to embedded devices, ensuring they do not contain maliciously crafted deep symlink nesting. 3) Restrict physical and local access to devices running U-Boot to prevent unauthorized firmware or filesystem modifications. 4) Incorporate secure boot mechanisms and firmware signing to prevent loading of unauthorized or tampered boot images. 5) Conduct regular security audits of embedded device firmware and bootloader configurations to detect anomalies. 6) Collaborate with device vendors and supply chain partners to ensure patched bootloader versions are integrated into device firmware. 7) Develop incident response plans that include recovery procedures for embedded device failures caused by bootloader issues. These steps go beyond generic advice by focusing on supply chain security, firmware validation, and physical access controls tailored to embedded environments common in Europe.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-01-09T00:00:00.000Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 690908557fff0e30cee23973

Added to database: 11/3/2025, 7:53:57 PM

Last enriched: 11/3/2025, 8:05:55 PM

Last updated: 12/19/2025, 4:18:54 PM

Views: 35

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

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