Cyber Resilience

CVE-2024-34476

Open5Gs ≤ 2.7.1

Published
05 May 2024
Modified
22 April 2025
Patch / advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0051 41th percentile
Risk Priority 45 floored blend · peak EPSS

Summary

CVE-2024-34476 is a medium-severity Buffer Access with Incorrect Length Value (CWE-805) vulnerability in Open5Gs Open5Gs. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 41th 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

Open5GS before 2.7.1 is vulnerable to a reachable assertion that can cause an AMF crash via NAS messages from a UE: ogs_nas_encrypt in lib/nas/common/security.c for pkbuf->len.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
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.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-44952Same product: Open5Gs Open5Gs
CVE-2025-44951Same product: Open5Gs Open5Gs
CVE-2026-2521Same product: Open5Gs Open5Gs
CVE-2026-2522Same product: Open5Gs Open5Gs
CVE-2026-8746Same product: Open5Gs Open5Gs
CVE-2024-40130Same product: Open5Gs Open5Gs
CVE-2024-40129Same product: Open5Gs Open5Gs
CVE-2026-8186Same product: Open5Gs Open5Gs
CVE-2025-29646Same product: Open5Gs Open5Gs
CVE-2025-15555Same product: Open5Gs Open5Gs

Affected Assets

open5gs
open5gs
≤ 2.7.1

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.4.1

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation (including fuzzing and static analysis) directly finds incorrect length values used in sequential buffer accesses.

Secure engineering principles require explicit bounds checking and correct length calculations when performing buffer operations.

Input validation rejects or corrects malformed length values supplied from external sources before they reach buffer operations.

Memory protection mechanisms limit the blast radius when an incorrect length value causes an out-of-bounds access.

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 prevent incorrect-length buffer operations via safe APIs, reviews, and testing.

ID.RA-01 partial match
prevents

Vulnerability identification can discover buffer-length flaws but does not prevent their introduction.

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 in development can detect out-of-bounds accesses, but does not guarantee prevention.

prevents

Secure development life cycle mandates buffer-safety practices that directly prevent incorrect length values.

prevents

Application security requirements can specify buffer-size validation, but do not prescribe implementation details.

prevents

Secure architecture principles encourage bounds-checked APIs, yet leave concrete coding decisions to developers.

prevents

Secure coding explicitly requires correct buffer-length handling, eliminating CWE-805 when followed.

References