High · published December 19, 2025
🚨 A conflicting address-family flag can crash your UPF! Just one mismatched setting in the PFCP Session Establishment Request could bring your service to its knees. 🔥 Think of it like a mismatched puzzle piece that almost fits but ultimately causes the entire picture to fall apart. When the CreatePDR PDI F-TEID address doesn't align with your DNN’s configuration, it’s like trying to connect two incompatible power adapters—it simply doesn’t work! This vulnerability can lead to a denial of service, meaning your network service could become entirely unavailable. If an attacker exploits this, they could cause crashes that interrupt critical communications, potentially leading to widespread outages in network services.
Think of it like a mismatched puzzle piece that almost fits but ultimately causes the entire picture to fall apart. When the CreatePDR PDI F-TEID address doesn't align with your DNN’s configuration, it’s like trying to connect two incompatible power adapters—it simply doesn’t work! The issue arises in Open5GS version 2.7.5-49-g465e90f, where an assertion failure in `lib/pfcp/context.c` occurs when the CreatePDR PDI F-TEID has a CH flag of 1 but mismatches the GTP-U resource family configured for the chosen DNN.
This vulnerability can lead to a denial of service, meaning your network service could become entirely unavailable. If an attacker exploits this, they could cause crashes that interrupt critical communications, potentially leading to widespread outages in network services. To remediate this vulnerability, ensure that the address-family flags for F-TEID are aligned with your GTP-U resource configuration. It’s also crucial to update your Open5GS to the latest version as soon as possible to incorporate any available fixes. You've got this! Follow these steps, and you’ll be a security hero in no time! 🛡️
| Product | Versions | Fixed in |
|---|---|---|
| open5gs/open5gs | all versions | — |