Executive brief
The Access and Mobility Management Function (AMF) component of the OMEC Project, which manages mobile network connections, is vulnerable to a denial-of-service attack. By sending a specially crafted network setup request, an attacker can cause the service to crash. This disruption can prevent mobile devices from connecting to the network, impacting service availability.
Technical details
A vulnerability exists in the omec-project AMF (Access and Mobility Management Function) up to version 2.1.3-dev. The flaw is located in the HandleNGSetupRequest function within ngap/handler.go, where the application fails to properly validate the InformationElement argument. Specifically, a malformed NGSetupRequest with missing or invalid information elements triggers a nil pointer dereference or an out-of-bounds memory access, leading to a Go runtime panic and service crash. This can be exploited remotely by an authenticated attacker (or a device with network access to the AMF) to cause a Denial of Service (DoS). The issue is addressed in version 2.2.0 by adding nil checks and input validation across the NGAP dispatcher and handlers.
Affected products
- omec-project amf < 2.2.0
Timeline
- 2026-04-21: patched: Fix merged in pull request 666
- 2026-04-23: disclosed: Issue 671 opened with reproduction steps
- 2026-05-18: advisory: GitHub Advisory and CVE published