free5GC
free5GC: NRF nnrf-nfm lacks NF Profile input validation — enables NF Registration Poisoning with arbitrary service endpoints
free5GC is an open-source implementation of the 5G core network. In 4.2.2 and earlier, the NRF RegisterNFInstance handler at PUT /nnrf-nfm/v1/nf-instances/{nfInstanceID} accepts NF Profiles without enforcing UUID format, nfStatus enum values, heartBeatTimer ranges, mandatory profile fields, or nfServices.ipEndPoints address constraints. The invalid profiles are persisted in the MongoDB NfProfile collection and returned by NFDiscover, allowing an attacker with SBI access to advertise attacker-controlled network-function endpoints and redirect control-plane signaling. This can expose credentials and signaling, alter service discovery integrity, and deny service across network functions that trust the NRF. This issue is fixed in version 4.2.3.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 4.2.3
Fixed in 4.2.3
Mitigation
Upgrade free5gc to 4.2.3 or later.
References
- Vendor advisory github.com/free5gc/free5gc/security/advisories…
- Patch github.com/free5gc/nrf/pull/90
- Patch github.com/free5gc/nrf/commit/bda0cf75be5556bb…
3 more
- Patch github.com/free5gc/nrf/commit/fcd3cfaa27cc4dc1…
- Release notes github.com/free5gc/free5gc/releases/tag/v4.2.3
- Release notes github.com/free5gc/nrf/releases/tag/v1.4.5
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.