2026-05-07 13:27 UTC
One malformed message. That's all it takes.
In our latest write-up, we show how a single UE- or gNB-originated signaling message can travel across the network and crash core functions that are not directly exposed — AMF, SMF, even MME in LTE.
Across both 5G and 4G, the same failure patterns appear:
Parsers assuming well-formed NAS payloads
NGAP handlers trusting mandatory IEs will always be present
EPCO fields that are forwarded untouched until they break the SMF
Stateful procedures that reach "should not happen" branches and terminate
Different stacks. Different protocols. Same outcome:
unexpected input → parser/state failure → process crash
These are not just "open source bugs." They are early warning signals for a wider class of parser and state machine risks that exist across mobile core implementations.
The key lesson is simple: proprietary does not mean fuzz tested. If your 5G or 4G core has not been tested with a stateful, protocol aware fuzzer, assume there are still crash paths hiding in the signaling stack.
Full breakdown here:
https://www.p1sec.com/blog/fuzzing-the-mobile-core-how-malformed-5g-4g-signaling-crashes-production-networks
Replies (0)
No replies.