CVE-2024-34475VulnerabilityPublished 4 May 2024Updated 2 Aug 2024

CVE-2024-34475: open5gs · n/a

Affects open5gsSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 2.7.1 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.7.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade open5gs/open5gs to 2.7.1.

Affected software

Product	Affected	Fixed in
GitHubopen5gs/open5gs`pkg:github/open5gs/open5gs`Other threats	Affected <2.7.1	Fixed in 2.7.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-34475, organizations should immediately upgrade Open5GS to version 2.7.1 or later, where the assertion failure has been addressed. If upgrading is not immediately feasible, network operators should implement strict filtering and validation of NAS messages at the network perimeter to block malformed or suspicious traffic targeting the AMF. Deploying anomaly detection systems that monitor for unusual NAS message patterns can help identify exploitation attempts early. Additionally, isolating the AMF component within a hardened and monitored environment reduces the risk of widespread impact. Operators should also conduct thorough testing of their 5G core implementations to identify any similar assertion or input validation issues. Regularly applying security patches and maintaining an up-to-date inventory of deployed Open5GS versions is critical. Finally, sharing threat intelligence and monitoring vulnerability disclosures related to Open5GS and 5G core components will help maintain proactive defenses.

Description

Open5GS before 2.7.1 is vulnerable to a reachable assertion that can cause an AMF crash via NAS messages from a UE: gmm_state_authentication in amf/gmm-sm.c for != OGS_ERROR.

Impact

The primary impact of CVE-2024-34475 is a denial of service condition on the AMF component of the Open5GS 5G core network. The AMF is responsible for critical functions such as mobility management, authentication coordination, and session management signaling. A crash of the AMF disrupts these functions, potentially causing service outages for subscribers connected to the affected network. This can lead to dropped connections, inability to authenticate new devices, and overall degradation of 5G network availability. For operators relying on Open5GS in production or test environments, this vulnerability could be exploited by attackers to cause network instability or outages remotely without needing credentials or user interaction. The impact is limited to availability, with no direct compromise of data confidentiality or integrity reported. However, the disruption of core network functions can have cascading effects on dependent services and user experience. Given the increasing adoption of 5G networks worldwide, any disruption in core network components can have significant operational and reputational consequences for service providers.

CWE-617Reachable Assertion (opens in a new tab)
Base weakness
The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.
Implementation
Make sensitive open/close operation non reachable by directly user-controlled data (e.g. open/close resources)
Implementation · Input Validation
Perform input validation on user data.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Mar 2026, 23:19 UTC

WeaknessesCWE-617

Technical details

References

Community reviews

Related threats