Security readout for executives and security teams
Plain-English summary
This CVE is an availability risk in Open5GS v2.4.11. A crafted PFCP packet can trigger a memory leak in the UPF PFCP path, potentially exhausting memory and causing denial of service. The sources do not identify active exploitation or a named fixed version.
Executive priority
Prioritize this for telecom, lab, or private 5G environments using Open5GS v2.4.11. Business risk is service disruption, not data theft, based on the supplied CVSS and description.
Technical view
CVE-2022-43221 is a CWE-401 memory leak in src/upf/pfcp-path.c in Open5GS v2.4.11. CVSS 3.1 is 7.5, network-reachable, low complexity, no privileges or user interaction, with high availability impact and no stated confidentiality or integrity impact.
Likely exposure
Exposure is most likely where Open5GS v2.4.11 UPF components process PFCP traffic from reachable networks. The CVE metadata lacks normalized affected vendor, product, version, and CPE entries, so inventory confirmation is required.
Exploitation context
The provided sources state denial of service through a crafted PFCP packet. CISA KEV is false, and no cited source confirms active exploitation. Public reference material exists, but evidence of real-world exploitation is not provided.
Researcher notes
The public record is sparse. The CVE description identifies Open5GS v2.4.11 and src/upf/pfcp-path.c, but structured affected metadata is empty. Treat fixed-version and exploit-status conclusions as unresolved unless confirmed from vendor guidance or additional sources.
Mitigation direction
- Identify Open5GS deployments and confirm whether v2.4.11 is running.
- Check official Open5GS guidance for fixed versions or recommended remediation.
- Restrict PFCP access to trusted control-plane peers only.
- Filter or rate-limit unexpected PFCP traffic at network boundaries.
- Monitor UPF memory growth and restart patterns until remediated.
Validation and detection
- Inventory Open5GS versions across UPF hosts and containers.
- Confirm whether PFCP interfaces are reachable from untrusted networks.
- Review UPF memory metrics for unexplained growth or restarts.
- Check firewall and segmentation rules around PFCP paths.
- Track vendor advisories because the provided sources do not name a fix.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-43221 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/ToughRunner/Open5gs_bugreport3CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.