dbcve.org
Open5gsApplication

CVE-2023-4882

HIGH · 7.5 CVSS v3.1 Published 2023-10-03
Fix available
A fix is available. Upgrade to after 2.4.10 or later.
See remediation →
84/100
Remediation priority · High
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
DOS vulnerability that could allow an attacker to register a new VNF (Virtual Network Function) value. This action could trigger the args_assets() function defined in the arg-log.php file, which would then execute the args-abort.c file, causing the service to crash.

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 denial-of-service vulnerability in the VNF (Virtual Network Function) registration process. Attackers can register a new VNF value that triggers the args_assets() function in arg-log.php, which then executes args-abort.c, causing the service to crash.

MitigationImplement input validation and bounds checking on VNF registration to prevent malformed input from triggering the crash. Investigate and fix the root cause in args_assets() and args-abort.c to handle edge cases gracefully.

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
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 checks

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

  1. Identify Open5gs installation version
    Check the installed version of Open5gs using package manager commands (dpkg -l open5gs, rpm -qa open5gs) or look for version information in /var/log/open5gs or the application's help output (open5gs --version). Compare against the vulnerable range <= 2.4.10.
    Affected if The installed version is 2.4.10 or lower.
  2. Locate the arg-log.php file
    Search for arg-log.php in the Open5gs installation directory, typically under /usr/lib/open5gs/webui or /opt/open5gs/lib/webui. Use: find /usr -name arg-log.php 2>/dev/null or ls -la in the suspected web root directories.
    Affected if The file exists and contains the args_assets() function referenced in the CVE.
  3. Verify args-abort.c is present
    Search for args-abort.c in the source or binary directories of the Open5gs installation. This file is part of the vulnerable code path that triggers the crash.
    Affected if The file exists in the installation, indicating the vulnerable code path is present.
  4. Check if web interface or API is exposed
    Review network configuration and running services to determine if the Open5gs web UI or REST API (which handles VNF registration) is exposed to network access. Check /etc/open5gs/*.yaml for bind addresses and listening ports.
    Affected if The VNF registration endpoint (typically part of the REST API on port 3000 or 8080) is accessible from network interfaces other than localhost.
  5. Identify VNF registration endpoint accessibility
    Examine the Open5gs configuration for NRF (Network Repository Function) or other components that handle VNF registration. Look for API endpoints under /nnrf-nfm/v1/nf-instances or similar paths in the configuration files.
    Affected if The VNF registration API endpoint is enabled and accessible, allowing arbitrary VNF value registration.

A user is affected if Open5gs version is 2.4.10 or lower, the vulnerable arg-log.php with args_assets() and args-abort.c files exist, and the VNF registration REST API endpoint is exposed and allows unauthenticated or authenticated registration of arbitrary VNF values that trigger the crash.

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.

From vendor data
Upgrade available Upgrade to a release after 2.4.10
Interim mitigation

Implement input validation and bounds checking on VNF registration to prevent malformed input from triggering the crash. Investigate and fix the root cause in args_assets() and args-abort.c to handle edge cases gracefully.

Fix this in Open5gs Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4882 — 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-4882 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