CVE-2023-23846
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDue to insufficient length validation in the Open5GS GTP library versions prior to versions 2.4.13 and 2.5.7, when parsing extension headers in GPRS tunneling protocol (GPTv1-U) messages, a protocol payload with any extension header length set to zero causes an infinite loop. The affected process becomes immediately unresponsive, resulting in denial of service and excessive resource consumption. CVSS3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:C
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpen5GS GTP library versions before 2.4.13 and 2.5.7 fail to validate extension header length when parsing GTPv1-U messages. When an extension header length is set to zero, the parsing code enters an infinite loop, causing the process to become unresponsive and resulting in denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.4.13= 2.5.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Open5GS installation and versionRun 'open5gs --version' or check package manager: 'dpkg -l | grep open5gs' or 'rpm -qa | grep open5gs'Affected if Installed version is less than 2.4.13 or equals 2.5.6
-
Verify GTP-U service is runningCheck for running Open5GS processes: 'ps aux | grep -E "(sgwu|smf|upf)" | grep -v grep' or check systemd services: 'systemctl list-units | grep open5gs'Affected if GTP-U handling services (SGWU, UPF) are running and the vulnerable code path is active
-
Confirm GTP-U port is listeningCheck if UDP port 2152 is open: 'ss -ulnp | grep 2152' or 'netstat -ulnp | grep 2152'Affected if GTP-U port 2152/UDP is listening, indicating the service accepts GTPv1-U packets
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.4.13
Upgrade Open5GS to version 2.4.13 or 2.5.7 or later to receive the length validation fix. Alternatively, restrict network access to GTP-U ports if upgrade is not immediately feasible.
Open5GS 2.4.13 or 2.5.7 (or later stable release)
- 1. Identify the currently installed Open5GS version by checking your package manager or running 'open5gs --version'
- 2. Determine which version branch you are currently running (2.4.x or 2.5.x)
- 3. For systems running Open5GS 2.4.x: Upgrade to version 2.4.13 or later
- 4. For systems running Open5GS 2.5.x: Upgrade to version 2.5.7 or later
- 5. Use your package manager to install the updated packages (e.g., 'apt update && apt upgrade' for Debian/Ubuntu, or 'yum/dnf update' for RHEL/CentOS)
- 6. Restart the Open5GS services to load the patched GTP library
- 7. Verify the new version is installed and services are running properly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23846 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-23846 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data