CVE-2023-4883
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 · uneditedInvalid pointer release vulnerability. Exploitation of this vulnerability could allow an attacker to interrupt the correct operation of the service by sending a specially crafted json string to the VNF (Virtual Network Function), and triggering the ogs_sbi_message_free function, which could cause a service outage.
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 · moderate confidenceA memory management vulnerability exists in the ogs_sbi_message_free function where an invalid pointer is released when processing a specially crafted JSON string sent to a Virtual Network Function (VNF). This leads to memory corruption and potential service outage.
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.10CVSS 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.
-
Identify Open5gs installation and versionRun 'open5gs --version' or check the installed package version using your system package manager (e.g., 'dpkg -l | grep open5gs' or 'rpm -qa | grep open5gs')Affected if The installed version is 2.4.10 or lower
-
Verify the SBI (Service-Based Interface) component is activeCheck if any Open5gs NRF, SMF, or UPF processes are running, as the ogs_sbi_message_free function handles SBI messages. Use 'ps aux | grep open5gs' or check systemctl status for open5gs-* servicesAffected if The SBI-related Open5gs services are running and exposed to network traffic
-
Confirm JSON input is accepted by the VNFReview the Open5gs configuration files (typically in /etc/open5gs/) for any NRF, SMF, or UPF configuration that enables HTTP REST API listeners. Check for 'sbi' or 'http' sections in the configAffected if The VNF is configured to accept HTTP/SBI connections from untrusted sources
-
Check for exposed SBI REST API endpointsUse 'netstat -tlnp' or 'ss -tlnp' to listen on ports 80, 443, or 7777 (common SBI ports). Also review firewall rules to determine if these ports are accessible from networkAffected if The SBI HTTP service ports are listening and accessible from network
You are affected if Open5gs version 2.4.10 or lower is installed and the SBI component is enabled and exposed to network traffic where a crafted JSON string could be received.
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 · scopedApply the vendor patch for CVE-2023-4883 which corrects the pointer validation in ogs_sbi_message_free, and validate all JSON input received by the VNF before processing.
Open5gs 2.6.7 or latest stable 2.x release (fixed version after 2.4.10)
- 1. Identify all Open5gs deployments running version 2.4.10 or earlier in your infrastructure
- 2. Backup all Open5gs configuration files and database data before upgrading
- 3. Stop all Open5gs services (amf, smf, upf, ausf, nrf, nssf, pcf, udm, udr, smf, etc.)
- 4. Download Open5gs version 2.6.7 or latest stable release from the official GitHub repository (https://github.com/open5gs/open5gs)
- 5. Compile and install the new version following the official installation instructions
- 6. Verify that the installed version is correct by running 'open5gs --version'
- 7. Restart all Open5gs services and verify they start without errors
- 8. Test basic 5G core functionality (registration, session establishment) to confirm the service operates correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4883 — 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-4883 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