Kurz gesagt
- CVE-2026-33062 ist eine Schwachstelle (HOCH (CVSS 7.5)) in github.com/free5gc/nrf, free5gc (free5gc).
- Wahrscheinlichkeit einer Ausnutzung in den nächsten 30 Tagen (EPSS): 0.69%, höher als bei 52.9% aller Schwachstellen.
- Abhilfe: auf 1.4.2 oder neuer aktualisieren.
Description
Impact
This is an Improper Input Validation vulnerability leading to Denial of Service.
- Security Impact: A remote attacker can cause the NRF service to panic and crash by sending a crafted HTTP GET request with a malformed
group-id-list parameter. This results in complete denial of service for the NRF discovery service.
- Functional Impact: The
EncodeGroupId function attempts to access array indices [0], [1], [2] without validating the length of the split data. When the parameter contains insufficient separator characters, the code panics with "index out of range".
- Affected Parties: All deployments of free5GC v4.0.1 using the NRF discovery service.
Patches
Yes, the issue has been patched.
The fix is implemented in PR free5gc/nrf#80 (commit: [add fix reference here]).
Users should upgrade to the next release of free5GC that includes this commit.
Workarounds
There is no direct workaround at the application level. The recommendation is to apply the provided patch or restrict access to the NRF API to trusted sources only.
NVD description
free5GC is an open source 5G core network. free5GC NRF prior to version 1.4.2 has an Improper Input Validation vulnerability leading to Denial of Service. All deployments of free5GC using the NRF discovery service are affected. The `EncodeGroupId` function attempts to access array indices [0], [1], [2] without validating the length of the split data. When the parameter contains insufficient separator characters, the code panics with "index out of range". A remote attacker can cause the NRF service to panic and crash by sending a crafted HTTP GET request with a malformed `group-id-list` parameter. This results in complete denial of service for the NRF discovery service. free5GC NRF version 1.4.2 fixes the issue. There is no direct workaround at the application level. The recommendation is to apply the provided patch or restrict access to the NRF API to trusted sources only.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free