Open5GS: Release of Invalid Pointer or Reference
CVE-2023-4883 is a high-severity release of invalid pointer or reference vulnerability in Open5GS, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Open5GS versions: 2.4.10 and prior. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.62% chance of exploitation within 30 days, higher than 50% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Open5GS you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (incibe.es) |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
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 cause a service outage.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Release of Invalid Pointer or Reference
The product attempts to return a memory resource to the system, but it calls the wrong release function or calls the appropriate release function incorrectly.
How developers prevent this class of flaw
- Only call matching memory management functions. Do not mix and match routines. For example, when you allocate a buffer with malloc(), dispose of the original pointer with free().
- When programming in C++, consider using smart pointers provided by the boost library to help correctly and consistently manage memory.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, glibc in Linux provides protection against free of invalid pointers.
More Release of Invalid Pointer or Reference vulnerabilities (CWE-763)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-open5gsThird Party Advisory
Other vulnerabilities in Open5GS
- 7.5 High severity
- 8.3 High severity
- 7.4 High severity
- 7.4 High severity
- 8.6 High severity
- 7.3 High severity
Recent Release of Invalid Pointer or Reference vulnerabilities
- 7.8 High severity
- 7.5 High severity
- 8.8 High severity
- 7.5 High severity
- 8.1 High severity
Spotted an error? Tell us.