Attack Chain

1. Attacker identifies a reachable NEF instance running free5GC v4.2.1.
2. Attacker crafts a malicious SMF callback request targeting the /nnef-callback/v1/notification/smf endpoint.
3. The attacker sets the Authorization header with a forged or arbitrary bearer token (e.g., Authorization: Bearer not-a-real-token).
4. The NEF server receives the request and, due to the missing authentication middleware, parses the request body without validating the token.
5. The callback handler within the NEF processes the request and attempts to look up subscription state using the provided NotifId.
6. If the NotifId is valid, the attacker can manipulate subscription data, leading to traffic-influence or PFD-management corruption.
7. The corrupted subscription data influences downstream SMF/UPF policy decisions, potentially diverting traffic or modifying service quality.
8. Attacker gains unauthorized control over network traffic and subscriber experience.

Impact

The lack of authentication on the nnef-callback route group allows any party that can reach the NEF on the SBI (Service Based Interface) to submit forged SMF callbacks anonymously. An attacker who can guess or obtain a valid NotifId can deliver forged event notifications against real subscription state, corrupting AF traffic-influence and PFD-management subscription views, and subsequently influencing downstream SMF/UPF policy decisions. The vulnerability can lead to unauthorized traffic diversion, service disruption, or modification of service quality for subscribers. The affected version is free5GC v4.2.1, potentially impacting deployments of this version in various telecommunications networks.

Recommendation

• Deploy the Sigma rule Detect Unauthenticated NEF Callback Request to identify attempts to exploit the vulnerability by detecting requests to the /nnef-callback/v1/notification/smf endpoint with invalid or suspicious authorization headers (see rule below).
• Monitor web server logs for unauthorized POST requests to the /nnef-callback/v1/notification/smf endpoint, referencing the IP address 10.100.200.19 from the provided PoC.
• Upgrade to a patched version of free5GC NEF that addresses the authentication vulnerability (see upstream fix at https://github.com/free5gc/nef/pull/24).
• Apply input validation and authorization checks on all SBI endpoints, especially callback handlers, to prevent unauthorized access and data manipulation.
• Review and harden the NEF configuration to ensure that only authorized services and endpoints are exposed, mitigating the risk of unauthorized access.