LiveActive security incident?Get immediate response
CVE Record

CVE-2022-43222: open5gs v2.4.11 was discovered to contain a memory leak in the component src/smf/pfcp-path.c.

open5gs v2.4.11 was discovered to contain a memory leak in the component src/smf/pfcp-path.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted PFCP packet.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-43222 is a denial-of-service risk in Open5GS v2.4.11. A crafted PFCP packet can trigger a memory leak in the SMF PFCP path code, potentially degrading or stopping service availability. The record rates this high because it is network-reachable and needs no authentication or user interaction.

Executive priority

Treat as a high-priority availability issue for any Open5GS v2.4.11 environment. It threatens service continuity, but current source evidence does not show data theft, integrity compromise, or active exploitation.

Technical view

The CVE describes CWE-401 memory leak behavior in open5gs v2.4.11, specifically src/smf/pfcp-path.c. CVSS 3.1 is 7.5 with AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, indicating remote unauthenticated availability impact only. The provided sources do not identify CPEs, affected version ranges beyond v2.4.11, or a fixed release.

Likely exposure

Exposure is most likely where Open5GS v2.4.11 SMF/PFCP functionality is deployed and PFCP traffic can reach it over the network. The source bundle does not provide CPEs or broader affected-version evidence.

Exploitation context

The CVE says denial of service is possible through a crafted PFCP packet. CISA KEV is false, and the provided sources do not document active exploitation, public weaponization, or exploitation in the wild.

Researcher notes

Evidence is sparse. The record identifies one affected version and component, a memory leak class, and a GitHub bug report reference. It does not provide a fix commit, complete affected range, exploit maturity, or vendor remediation details.

Mitigation direction

  • Identify any Open5GS v2.4.11 deployments, especially SMF/PFCP components.
  • Check Open5GS or vendor guidance for fixed versions or official patches.
  • Restrict PFCP reachability to trusted peers and management networks only.
  • Monitor SMF memory growth, restarts, and availability until remediation is confirmed.

Validation and detection

  • Confirm Open5GS versions deployed in production, lab, and backup environments.
  • Verify whether affected SMF/PFCP code is present and enabled.
  • Review network controls limiting PFCP traffic sources.
  • Check logs and monitoring for SMF memory exhaustion or unexplained DoS symptoms.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2022-43222 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2022-43222Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-401 · source CWE mapping

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.