Security Resilience

CVE-2023-37018

Open5Gs ≤ 2.6.4

Public PoC
Published
22 January 2025
Modified
22 April 2025
CVSS Score v3.1 8.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
EPSS Score 0.0078 56th percentile
Risk Priority 63 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-37018 is a high-severity Reachable Assertion (CWE-617) vulnerability in Open5Gs. Its CVSS base score is 8.6 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Defense Impairment (T1687); ranked in the top 44% 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-2023-37018 is a vulnerability in Open5GS Mobility Management Entity (MME) versions up to and including 2.6.4. It involves a reachable assertion (CWE-617) that can be remotely triggered by a malformed ASN.1 packet over the S1AP interface. An attacker sends a UE Capability Info Indication message missing the required MME_UE_S1AP_ID field, causing the assertion to fail.

The vulnerability has a CVSS v3.1 base score of 8.6 (AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H), indicating high severity due to network accessibility, low attack complexity, no privileges or user interaction required, changed scope, and high availability impact. Any unauthenticated remote attacker with access to the S1AP interface can exploit it by transmitting the malformed message, crashing the MME process. Repeated exploitation results in sustained denial of service against the MME.

Mitigation details are available in the advisory published at https://cellularsecurity.org/ransacked.

EU & UK References

Vulnerability Data

Open5GS MME versions <= 2.6.4 contains an assertion that can be remotely triggered via a malformed ASN.1 packet over the S1AP interface. An attacker may send a `UE Capability Info Indication` message missing a required `MME_UE_S1AP_ID` field to repeatedly crash…

more

the MME, resulting in denial of service.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1687 Exploitation for Defense Impairment Defense Impairment
Adversaries may exploit vulnerabilities in security software, infrastructure, or defensive components to degrade, disable, or otherwise continue to impair their ability to prevent, detect, or respond to malicious activity.
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.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-37016Same product: Open5Gs Open5Gs
CVE-2023-37002Same product: Open5Gs Open5Gs
CVE-2024-24427Same product: Open5Gs Open5Gs
CVE-2023-37003Same product: Open5Gs Open5Gs
CVE-2023-37005Same product: Open5Gs Open5Gs
CVE-2026-2523Same product: Open5Gs Open5Gs
CVE-2023-37004Same product: Open5Gs Open5Gs
CVE-2023-37011Same product: Open5Gs Open5Gs
CVE-2025-9405Same product: Open5Gs Open5Gs
CVE-2025-6952Same product: Open5Gs Open5Gs

Affected Assets

open5gs
open5gs
≤ 2.6.4

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation finds reachable assertions during development.

Security engineering principles discourage use of assertions for handling untrusted input.

Validating untrusted inputs structurally prevents attacker data from reaching and triggering assertions.

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
blocks

Secure SDLC practices directly prevent unsafe assertions from being coded in reachable paths.

DE.CM-09 partial match
blocks

Runtime monitoring of software can detect assertion-triggered crashes as adverse events.

ID.RA-01 partial match
blocks

Vulnerability identification processes can discover and record reachable-assertion flaws before deployment.

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 reachable assertions before release, reducing the likelihood of exploitation.

prevents

Secure coding standards explicitly ban the use of assert() or equivalent statements that can be triggered by external input.

References