Cyber Resilience

CVE-2024-8447

Published
02 January 2025
Modified
15 April 2026
CVSS Score v3.1 5.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0062 47th percentile
Risk Priority 47 floored blend · peak EPSS

Summary

CVE-2024-8447 is a medium-severity Deadlock (CWE-833) vulnerability. Its CVSS base score is 5.9 (Medium).

Operationally, ranked at the 47th 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 SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

A security issue was discovered in the LRA Coordinator component of Narayana. When Cancel is called in LRA, an execution time of approximately 2 seconds occurs. If Join is called with the same LRA ID within that timeframe, the application…

more

may crash or hang indefinitely, leading to a denial of service.

CWE(s)
CWE-833

Related Threats

CVEs Like This One

CVE-2025-36010Shared CWE-833
CVE-2025-10150Shared CWE-833
CVE-2026-70616Shared CWE-833
CVE-2025-21313Shared CWE-833
CVE-2025-1713Shared CWE-833
CVE-2024-47506Shared CWE-833
CVE-2025-8312Shared CWE-833
CVE-2026-33904Shared CWE-833
CVE-2023-31084Shared CWE-833
CVE-2025-59463Shared CWE-833

Affected Assets

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)
  • V15.4.3

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation activities can exercise concurrent paths and resource contention to discover deadlock conditions before deployment.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles applied during design can incorporate synchronization ordering, timeouts, and resource hierarchies that structurally avoid deadlock formation.

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 partial match
prevents

Secure SDLC practices can include concurrency analysis and lock discipline to avoid deadlock conditions.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect deadlock conditions through stress and concurrency testing.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle requires deadlock analysis and avoidance techniques during design and coding.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture principles include concurrency controls and resource-locking discipline that prevent deadlock.

A.8.28 Secure coding partial match
prevents

Secure coding standards mandate safe lock ordering, timeouts, and deadlock detection patterns.

A.8.32 Change management none match
none

Change management may catch deadlock-related defects during reviews but does not directly address concurrency design.

References