Security readout for executives and security teams
Plain-English summary
Open5GS 2.4.11 has a memory leak in ngap-handler.c. A remote, unauthenticated actor able to send crafted UE attachment traffic may exhaust memory and disrupt service availability. The provided sources do not identify data theft or integrity impact.
Executive priority
Prioritize remediation where Open5GS supports business-critical telecom, private 5G, or customer-facing testing. The business risk is service outage rather than confirmed compromise, but unauthenticated network reachability raises operational urgency.
Technical view
CVE-2022-43223 is a CWE-401 memory leak in Open5GS ngap-handler.c. CVSS 3.1 is 7.5: network reachable, low complexity, no privileges, no user interaction, high availability impact. The described trigger is crafted UE attachment traffic causing denial of service.
Likely exposure
Likely exposure is limited to organizations running Open5GS v2.4.11, especially lab, private 5G, telecom, or test-core environments where UE attachment handling is reachable.
Exploitation context
The source bundle describes denial of service through crafted UE attachment traffic. It does not show CISA KEV listing, active exploitation, public exploitation at scale, or a named fixed release.
Researcher notes
Evidence is narrow: the CVE record and referenced bug report identify a memory leak and DoS trigger, but the bundle lacks patch metadata, affected CPEs, exploit maturity, or operational indicators. Validate exposure before assuming broad product impact.
Mitigation direction
- Inventory Open5GS deployments and confirm whether version 2.4.11 is in use.
- Check Open5GS project guidance, release notes, and maintainer advisories for fixed versions.
- Restrict network access to Open5GS control-plane interfaces to trusted sources only.
- Monitor Open5GS memory use and restart patterns for abnormal growth.
- Treat exposed test or lab cores as production risk until assessed.
Validation and detection
- Confirm installed Open5GS version and whether ngap-handler.c is present in the deployment.
- Review network paths that can reach UE attachment handling components.
- Check service logs and monitoring for memory growth during attachment activity.
- Review change history for upgrades after Open5GS 2.4.11.
- Document any compensating controls limiting untrusted attachment traffic.
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-43223 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_bugreport2CVE 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.