dbcve.org
Open5gsApplication

CVE-2023-4885

MEDIUM · 5.9 CVSS v3.1 Published 2023-10-03
Fix available
A fix is available. Upgrade to after 2.4.10 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Man in the Middle vulnerability, which could allow an attacker to intercept VNF (Virtual Network Function) communications resulting in the exposure of sensitive information.

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 confidence

A Man-in-the-Middle (MitM) vulnerability in Virtual Network Function (VNF) communications allows an attacker positioned on the network path to intercept and eavesdrop on VNF-to-VNF or VNF-to-management plane traffic, potentially exposing sensitive data in transit.

MitigationImplement mutual TLS (mTLS) authentication for all VNF communications, enforce network segmentation to prevent unauthorized network positioning, and deploy certificate pinning to ensure communication integrity.

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
Open5gsApplication
Affected:<= 2.4.10

CVSS 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Open5gs version
    Run 'open5gs --version' or check the package manager for the installed version (e.g., dpkg -l open5gs, rpm -qi open5gs)
    Affected if The installed version is 2.4.10 or lower
  2. Determine if TLS encryption is enforced for VNF communications
    Inspect the Open5gs configuration files (typically in /etc/open5gs/ or /opt/open5gs/etc/) for TLS-related settings in NRF, NSSF, and other VNF configuration files
    Affected if TLS is not explicitly enabled or 'tls_verify' is set to 'off' in VNF communication settings
  3. Verify if mutual TLS (mTLS) is configured for inter-VNF authentication
    Check the configuration files for 'mutual_tls' or 'client_certificate' settings in the VNF components
    Affected if mTLS is not configured or client certificate authentication is disabled for VNF-to-VNF traffic
  4. Inspect network configuration for VNF communication channels
    Review the freeDiameter or other Diameter/S1AP configuration files used for VNF intercommunication
    Affected if The configuration allows plaintext or unauthenticated connections between VNFs or to the management plane
  5. Confirm the deployment uses TLS 1.2 or higher for VNF traffic
    Check for 'tls_version_min' or similar settings in the Open5gs configuration
    Affected if TLS version is set below 1.2 or TLS is not required for VNF communications

A user is affected if they are running Open5gs version 2.4.10 or lower and TLS/mTLS is not enforced for VNF-to-VNF or VNF-to-management plane communications.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 2.4.10
Interim mitigation

Implement mutual TLS (mTLS) authentication for all VNF communications, enforce network segmentation to prevent unauthorized network positioning, and deploy certificate pinning to ensure communication integrity.

Recommended fix Moderate confidence

Open5GS 2.4.11 or later stable release

  1. 1. Identify the current Open5GS version installed using the package manager or binary version check
  2. 2. Stop all Open5GS services before upgrading to prevent service interruption
  3. 3. Update the package repository to ensure access to the latest packages
  4. 4. Upgrade Open5GS to version 2.4.11 or the latest stable release available in the repository
  5. 5. Verify the installed version matches the expected fixed version
  6. 6. Restart Open5GS services and confirm all components are running
  7. 7. Test VNF communications to ensure the upgrade did not introduce regressions
Caveat Review release notes for any configuration changes or deprecated features between 2.4.10 and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Open5gs Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4885 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-4885 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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