Description
free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's BSF PUT /nbsf-management/v1/subscriptions/{subId} handler has an unsynchronized write on the global Subscriptions map. The handler first reads the map under RLock() via BSFContext.GetSubscription(subId), but if the subscription does not exist, ReplaceIndividualSubcription() writes back to the same map directly without taking the mutex (bsfContext.BsfSelf.Subscriptions[subId] = subscription). Under concurrent authenticated PUT load, one goroutine can read while another writes the map, which causes the Go runtime to abort the process with fatal error: concurrent map read and map write (Go runtime panics that come from concurrent map access bypass recover() and terminate the process). The BSF container exits with code 2 -- the entire BSF SBI surface goes down until restart. This vulnerability is fixed in 4.2.2.
Problem types
CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
CWE-820: Missing Synchronization
Product status
References
github.com/...ree5gc/security/advisories/GHSA-27ph-8q4f-h7m7
github.com/free5gc/free5gc/issues/926
github.com/...ree5gc/security/advisories/GHSA-27ph-8q4f-h7m7
github.com/free5gc/free5gc/issues/926
github.com/...ommit/277908565fd628d974a13ef562b81a8b7b519ffa