Cyber Resilience

CVE-2024-0151

Published
24 April 2024
Modified
15 April 2026
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
EPSS Score 0.0045 37th percentile
Risk Priority 50 floored blend · peak EPSS

Summary

CVE-2024-0151 is a medium-severity Improper Handling of Unexpected Data Type (CWE-241) vulnerability in Arm (inferred from references). Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 37th 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

Insufficient argument checking in Secure state Entry functions in software using Cortex-M Security Extensions (CMSE), that has been compiled using toolchains that implement 'Arm v8-M Security Extensions Requirements on Development Tools' prior to version 1.4, allows an attacker to pass…

more

values to Secure state that are out of range for types smaller than 32-bits. Out of range values might lead to incorrect operations in secure state.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-9423Shared CWE-241
CVE-2025-63548Shared CWE-241
CVE-2025-1004Shared CWE-241
CVE-2024-25966Shared CWE-241
CVE-2024-21935Shared CWE-241
CVE-2025-2268Shared CWE-241
CVE-2024-32268Shared CWE-241
CVE-2025-7339Shared CWE-241
CVE-2026-47110Shared CWE-241
CVE-2024-37316Shared CWE-241

Affected Assets

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

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Input validation explicitly checks that supplied data matches expected types and rejects mismatches before they reach processing logic.

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 proper input validation and type checking to prevent this weakness.

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 type-handling flaws but does not itself implement the preventive control.

prevents

Secure development lifecycle includes input validation and type checking that directly mitigates improper handling of unexpected data types.

prevents

Application security requirements typically mandate strong input validation and type enforcement to prevent malformed data processing.

prevents

Secure system architecture principles encourage robust input handling but do not specifically address data-type validation.

prevents

Secure coding standards explicitly require type checking and input sanitization, directly addressing improper handling of unexpected data types.

References