Cyber Resilience

CVE-2024-58251

Published
23 April 2025
Modified
17 June 2026
CVSS Score v3.1 2.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L
EPSS Score 0.0017 7th percentile
Risk Priority 23 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-58251 is a low-severity Improper Neutralization of Escape, Meta, or Control Sequences (CWE-150) vulnerability in Busybox (inferred from references). Its CVSS base score is 2.5 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 7th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

In netstat in BusyBox through 1.37.0, local users can launch of network application with an argv[0] containing an ANSI terminal escape sequence, leading to a denial of service (terminal locked up) when netstat is used by a victim.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-39342Shared CWE-150
CVE-2025-55193Shared CWE-150
CVE-2026-49147Shared CWE-150
CVE-2026-39879Shared CWE-150
CVE-2024-47252Shared CWE-150
CVE-2023-26055Shared CWE-150
CVE-2025-47284Shared CWE-150
CVE-2025-0975Shared CWE-150
CVE-2024-33899Shared CWE-150
CVE-2025-64494Shared CWE-150

Affected Assets

Busybox
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.10
  • V1.3.12

Mitigating Controls (NIST 800-53 r5) AI

SI-10 requires validation/sanitization of inputs that directly stops escape/meta/control sequences from reaching downstream components.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input neutralization and escaping to prevent this class of flaw.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect the weakness but does not itself implement neutralization.

prevents

Secure development lifecycle mandates input validation and output encoding that directly neutralizes escape/meta sequences.

prevents

Application security requirements explicitly call for controls against injection and malformed input sequences.

prevents

Secure architecture principles reduce attack surface but do not prescribe specific neutralization techniques.

prevents

Secure coding standards require proper escaping and neutralization of control characters before downstream processing.

References