Security readout for executives and security teams
Plain-English summary
Open5GS versions 2.4.12/2.5.6 and earlier can be forced into a denial of service while handling certain GTPv1-U messages. The vulnerable process becomes unresponsive and consumes resources. This matters most for organizations using Open5GS in telecom or lab mobile-core environments where GTP traffic can reach the affected service.
Executive priority
Treat this as a high-priority availability risk for Open5GS-backed mobile-core services. It does not indicate data theft or integrity compromise, but a reachable vulnerable service may be made unresponsive with low attacker effort.
Technical view
The Open5GS GTP library lacks sufficient length validation when parsing GTPv1-U extension headers. An extension header length of zero can trigger an infinite loop, making the affected process immediately unresponsive. The issue is network-reachable, unauthenticated, low complexity, and impacts availability only. Fixed versions are 2.4.13 and 2.5.7.
Likely exposure
Exposure is likely limited to environments running Open5GS versions <=2.4.12 or <=2.5.6 where GTPv1-U traffic can reach affected Open5GS processes. Internet exposure is not established in the provided sources.
Exploitation context
The CVSS vector indicates network attackability without privileges or user interaction. The sources describe proof-of-concept exploit maturity, but CISA KEV is false and the bundle provides no evidence of active exploitation.
Researcher notes
Focus validation on version exposure and reachability, not reproducing the parser fault. The relevant weakness is insufficient validation of GTPv1-U extension header length in the Open5GS GTP library, associated with CWE-770 and high availability impact.
Mitigation direction
- Upgrade Open5GS to 2.4.13, 2.5.7, or later supported releases.
- Restrict GTPv1-U access to trusted network paths only.
- Monitor affected Open5GS processes for hangs, restarts, and resource exhaustion.
- Review current Open5GS vendor guidance before production remediation.
- Prioritize patching systems carrying operational telecom traffic.
Validation and detection
- Inventory Open5GS deployments and record exact package or build versions.
- Confirm no deployment remains on 2.4.12, 2.5.6, or earlier.
- Map which interfaces can receive GTPv1-U traffic.
- Check firewall and routing controls around GTP-facing services.
- Review process health metrics for historical denial-of-service symptoms.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-23846 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.