omec-project UPF vulnerabilities

A flaw has been found in omec-project UPF up to 2.1.3-dev. This affects the function handleSessionEstablishmentRequest in the file /pfcpiface/pfcpiface/messages_session.go. The manipulation causes a null pointer dereference. The attack may be initiated remotely, and the exploit has been published.

In the omec-project UPF (pfcpiface component) version upf-epc-pfcpiface:2.1.3-dev, there is a denial-of-service vulnerability. When the UPF receives a PFCP Session Report Response missing the mandatory Cause Information Element, the session report handler dereferences a nil pointer instead of rejecting the malformed message, causing a panic and terminating the UPF process.

A denial-of-service vulnerability exists in the omec-project UPF (pfcpiface component) version 2.1.3-dev. After PFCP association, a specially crafted PFCP Session Establishment Request with a CreatePDR containing a malformed Flow-Description is not robustly validated; the parseFlowDesc parser can read beyond the buffer, causing a panic and terminating the UPF process.

A denial-of-service vulnerability exists in the omec-project UPF (pfcpiface component) version 2.1.3-dev. After PFCP association is established, a PFCP Session Establishment Request missing the mandatory F-SEID (CPF-SEID) Information Element is not properly validated; the handler calls IE.FSEID() on a nil pointer, triggering a panic and terminating the UPF process.

A denial-of-service vulnerability exists in the omec-project UPF (component upf-epc/pfcpiface) up to at least version upf-epc-pfcpiface:2.1.3-dev. When the UPF receives a PFCP Association Setup Request that is missing the mandatory NodeID Information Element, the association setup handler dereferences a nil pointer instead of validating the message, causing a panic and terminating the UPF process. An attacker who can send PFCP Association Setup Request messages to the UPF's N4/PFCP endpoint can exploit this issue to repeatedly crash the UPF and disrupt user-plane services.