Service crash via unreleased PFCP nodes
Published Nov 1, 2022 · Updated May 2, 2025
Memory leak in the SMF PFCP handler in Open5GS 2.4.11 allows remote attackers to crash the service with crafted PFCP packets. The pfcp_recv_cb function allocates a node for each previously unseen PFCP source and retains it in a fixed-size 64-entry pool until SMF terminates. No authentication or user interaction is required; more than 64 invalid packets sent through different sockets exhaust the pool and crash SMF.
Summary
What happened
Memory leak in the SMF PFCP handler in Open5GS 2.4.11 allows remote attackers to crash the service with crafted PFCP packets. The pfcp_recv_cb function allocates a node for each previously unseen PFCP source and retains it in a fixed-size 64-entry pool until SMF terminates. No authentication or user interaction is required; more than 64 invalid packets sent through different sockets exhaust the pool and crash SMF.
The record
- CVE
- CVE-2022-43222
- Published
- Nov 1, 2022
- Updated
- May 2, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 1, 2022CVE publishedPublication date reported by the CVE source.
- May 2, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Open5GS SMF PFCP node-pool exhaustion proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo