Cyber Resilience

CVE-2024-51179

Open5Gs 2.7.1

Public PoC
Published
12 November 2024
Modified
29 September 2025
CVSS Score v3.1 7.5
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:H
EPSS Score 0.010 61th percentile
Risk Priority 68 floored blend · peak EPSS

Summary

CVE-2024-51179 is a high-severity Improper Resource Shutdown or Release (CWE-404) vulnerability in Open5Gs Open5Gs. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 39% of CVEs by exploit likelihood; 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 SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-51179 is a denial-of-service vulnerability in Open5GS version 2.7.1 that affects core 5G network functions, specifically the User Plane Function and Session Management Function during the Packet Data Unit session establishment process. The flaw is tracked under CWE-404 and carries a CVSS 3.1 score of 7.5, reflecting network-accessible attack vectors that require no authentication or user interaction and result in high availability impact.

A remote attacker can send crafted traffic to trigger the vulnerability in the NFV components handling PDU sessions, causing the affected functions to fail and disrupting service continuity for connected users. Because the attack requires only network reachability, it can be launched from any position that can reach the exposed 5G core interfaces.

The single public reference is a GitHub repository that documents the issue; no vendor advisory, patch details, or mitigation guidance is provided in the available sources. The associated EPSS score has remained flat at 0.1354 with no material increase since disclosure.

EU & UK References

Vulnerability Data

An issue in Open 5GS v.2.7.1 allows a remote attacker to cause a denial of service via the Network Function Virtualizations (NFVs) such as the User Plane Function (UPF) and the Session Management Function (SMF), The Packet Data Unit (PDU)…

more

session establishment process.

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.
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.001 OS Exhaustion Flood Impact
Adversaries may launch a denial of service (DoS) attack targeting an endpoint's operating system (OS).
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-1587Same product: Open5Gs Open5Gs
CVE-2025-15418Same product: Open5Gs Open5Gs
CVE-2026-8120Same product: Open5Gs Open5Gs
CVE-2026-8119Same product: Open5Gs Open5Gs
CVE-2026-8123Same product: Open5Gs Open5Gs
CVE-2026-8744Same product: Open5Gs Open5Gs
CVE-2026-8251Same product: Open5Gs Open5Gs
CVE-2025-5935Same product: Open5Gs Open5Gs
CVE-2025-1925Same product: Open5Gs Open5Gs
CVE-2026-7587Same product: Open5Gs Open5Gs

Affected Assets

open5gs
open5gs
2.7.1

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover missing or incorrect resource releases after code is written.

Engineering principles can require explicit resource acquisition/release patterns that stop improper shutdown from being introduced.

Priority-based resource allocation limits the blast radius when released resources are not returned to the pool.

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 include coding standards for correct resource allocation and release.

DE.CM-09 partial match
prevents

Runtime monitoring can detect resource exhaustion caused by improper shutdown or release.

ID.AM-08 partial match
prevents

Lifecycle management of assets can encompass proper resource release at end-of-life or shutdown.

PR.IR-04 partial match
prevents

Capacity management helps surface leaks from unreleased resources but does not prevent the coding 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.

prevents

Including restart, recovery and media-handling instructions reduces the likelihood that resources or sensitive data will be left in an exposed or improperly released state after a failure.

References