Security Resilience

CVE-2023-4883

Open5Gs ≤ 2.4.10

Published
03 October 2023
Modified
21 November 2024
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0062 48th percentile
Risk Priority 58 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-4883 is a high-severity Release of Invalid Pointer or Reference (CWE-763) vulnerability in Open5Gs Open5Gs. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked at the 48th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

Invalid 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…

more

cause a service outage.

CWE(s)
CWE-763

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.001 Junk Data Command And Control
Adversaries may add junk data to protocols used for command and control to make detection more difficult.
attack.mitre.org →
T1003 OS Credential Dumping Credential Access
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password.
attack.mitre.org →
T1003.001 LSASS Memory Credential Access
Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS).
attack.mitre.org →
T1003.006 DCSync Credential Access
Adversaries may attempt to access credentials and other sensitive information by abusing a Windows Domain Controller's application programming interface (API)(Citation: Microsoft DRSR Dec 2017) (Citation: Microsoft GetNCCChanges) (Citati…
attack.mitre.org →
T1006 Direct Volume Access Stealth
Adversaries may directly access a volume to bypass file access controls and file system monitoring.
attack.mitre.org →
T1010 Application Window Discovery Discovery
Adversaries may attempt to get a listing of open application windows.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-40129Same product: Open5Gs Open5Gs
CVE-2024-40130Same product: Open5Gs Open5Gs
CVE-2025-15555Same product: Open5Gs Open5Gs
CVE-2026-8252Same product: Open5Gs Open5Gs
CVE-2026-2062Same product: Open5Gs Open5Gs
CVE-2025-55904Same product: Open5Gs Open5Gs
CVE-2025-14953Same product: Open5Gs Open5Gs
CVE-2023-23846Same product: Open5Gs Open5Gs
CVE-2026-8186Same product: Open5Gs Open5Gs
CVE-2026-8746Same product: Open5Gs Open5Gs

Affected Assets

open5gs
open5gs
≤ 2.4.10

Mitigating Controls

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 partial match
blocks

Secure SDLC practices directly prevent invalid pointer release errors during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.25 Secure development life cycle partial match
blocks

A.8.25 mandates a secure-SDLC process (requirements, checkpoints, secure coding guidelines, testing, training) but does not itself stop an invalid pointer/reference from being released; the coding defect can still be written, reach production, and be exploitable.

A.8.26 Application security requirements partial match
blocks

A.8.26 only requires that security requirements (including resilience against attacks such as buffer overflows) be identified and specified during development; it does not itself enforce, implement or assure those requirements, so the invalid-pointer weakness can still arise and be exploited.

A.8.27 Secure system architecture and engineering principles partial match
blocks

A.8.27 mandates establishing and applying secure engineering principles (e.g. least privilege, security by design, hardening) during architecture and development; it does not stop an invalid pointer release from being exploitable once the coding error exists in the product.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prohibit mismatched or incorrect pointer-release calls.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing can detect invalid pointer releases before release.

A.8.8 Management of technical vulnerabilities partial match
removes

References