Cyber Resilience

CVE-2024-5754

Zephyrproject Zephyr ≤ 3.6.0

Public PoC
Published
13 September 2024
Modified
17 September 2025
Patch / advisory
CVSS Score v3.1 8.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
EPSS Score 0.0031 23th percentile
Risk Priority 58 floored blend · peak EPSS

Summary

CVE-2024-5754 is a high-severity Reliance on Untrusted Inputs in a Security Decision (CWE-807) vulnerability in Zephyrproject Zephyr. Its CVSS base score is 8.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 23th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

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

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

BT: Encryption procedure host vulnerability

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.
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
T1556 Modify Authentication Process Defense Impairment
Adversaries may modify authentication mechanisms and processes to access user credentials or enable otherwise unwarranted access to accounts.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-8023Same product: Zephyrproject Zephyr
CVE-2026-10671Same product: Zephyrproject Zephyr
CVE-2024-11263Same product: Zephyrproject Zephyr
CVE-2026-10647Same product: Zephyrproject Zephyr
CVE-2025-10458Same product: Zephyrproject Zephyr
CVE-2025-10456Same product: Zephyrproject Zephyr
CVE-2023-4424Same product: Zephyrproject Zephyr
CVE-2023-7060Same product: Zephyrproject Zephyr
CVE-2026-10653Same product: Zephyrproject Zephyr
CVE-2026-10685Same product: Zephyrproject Zephyr

Affected Assets

zephyrproject
zephyr
≤ 3.6.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

Explicitly requires that every access decision be based on authoritative, protected decision data rather than caller-supplied inputs.

Input validation can reject malformed or attacker-controlled values before they reach a security decision point.

Access enforcement requires decisions to be made from trusted policy data rather than modifiable client-supplied inputs.

Information-flow enforcement applies rules to validated, internal attributes instead of untrusted external values.

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.AA-03 mostly match
prevents

Strong authentication mechanisms directly prevent security decisions from depending on modifiable, untrusted inputs.

PR.AA-04 mostly match
prevents

Verification and protection of identity assertions stops reliance on attacker-controlled values for authorization decisions.

PR.AA-01 partial match
prevents

Proper management of identities/credentials reduces the chance that security decisions will be driven by untrusted inputs.

PR.AA-05 partial match
prevents

Policy-driven, least-privilege authorization reduces opportunities to bypass controls via tampered inputs.

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.

prevents

Secure coding standards directly prohibit using untrusted inputs for security-critical decisions.

finds

Security testing in development catches input-validation flaws before deployment.

finds

Monitoring can detect exploitation but does not stop the underlying weakness.

prevents

Application security requirements explicitly call for validation of inputs used in security decisions.

prevents

Secure architecture principles mandate treating all external inputs as untrusted.

prevents

Access-control rules can be bypassed if they rely on untrusted inputs.

References