LiveActive security incident?Get immediate response
CVE Record

CVE-2024-14043: Open5GS Diameter S6a mme-fd-path.c mme_s6a_subscription_data_from_avp heap-based overflow

A vulnerability was determined in Open5GS up to 2.7.1. This vulnerability affects the function mme_s6a_subscription_data_from_avp of the file src/mme/mme-fd-path.c of the component Diameter S6a Interface. Executing a manipulation of the argument msisdn_len can lead to heap-based buffer overflow. It is possible to launch the attack remotely. The exploit has been publicly disclosed and may be utilized. Upgrading to version 2.7.2 is able to resolve this issue. This patch is called 7ea82cb87bb65c3694d8d7c7a5efed1c4d3c9304. Upgrading the affected component is recommended.

MediumCVSS 6.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Open5GS versions through 2.7.1 can mishandle specially formed subscriber data received through the Diameter S6a interface, causing memory corruption. A successful attack could affect confidentiality, integrity, or service availability. The attack is remote but the supplied CVSS vector indicates authentication is required.

Executive priority

Prioritize remediation for production mobile-core environments using the affected S6a path, especially where peer trust is broad or uncertain. Upgrade promptly through normal change control. The moderate rating reflects authentication requirements and absent evidence of active exploitation, while public proof-of-concept material raises urgency.

Technical view

The mme_s6a_subscription_data_from_avp function in src/mme/mme-fd-path.c insufficiently handles attacker-influenced msisdn_len data, allowing a heap-based buffer overflow while parsing a Diameter S6a subscription-data AVP. The issue is classified as CWE-119 and CWE-122 and is fixed by commit 7ea82cb87bb65c3694d8d7c7a5efed1c4d3c9304.

Likely exposure

Exposure is most likely where Open5GS 2.7.1 or earlier runs the MME Diameter S6a interface and can receive malicious subscription data from an authenticated source. The bundle inconsistently lists 2.7.2 as affected while also identifying it as the fixed release; verify the installed code contains the cited patch.

Exploitation context

A proof-of-concept artifact has been publicly disclosed, increasing practical risk. However, the source bundle does not establish active exploitation, and this CVE is not listed as KEV. The CVSS vector indicates remote, low-complexity exploitation requiring authentication.

Researcher notes

The supplied record reports a remotely triggerable heap overflow involving msisdn_len and provides a public capture artifact. It does not document observed exploitation or establish a specific outcome beyond possible memory corruption. The affected-version array conflicts with the narrative and release guidance regarding 2.7.2, so patch-presence verification is important.

Mitigation direction

  • Upgrade Open5GS to version 2.7.2 or a later vendor-supported release.
  • Confirm the deployment contains commit 7ea82cb87bb65c3694d8d7c7a5efed1c4d3c9304.
  • Restrict Diameter S6a connectivity to explicitly trusted and authenticated peers.
  • Review Open5GS vendor guidance for any additional operational mitigations.

Validation and detection

  • Inventory Open5GS instances and record their exact installed versions.
  • Verify the deployed source or package includes the cited corrective commit.
  • Identify systems exposing or using the Diameter S6a interface.
  • Review which authenticated peers can supply subscription data to affected MME instances.
  • Test remediation safely in a controlled environment without replaying public exploit artifacts.
Prepared
Confidence
high
Sources
6

Public sources used

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

CWE-122: 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-2024-14043 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
Medium
CVSS
6.5 (2.0)
Known Exploited
No
Published

Vector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:OF/RC:C

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.

4CVSS vectors
6Timeline events
1ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

CVSS vector scores

4 official scores

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
6.5CVSS 2.0MediumAV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:OF/RC:C86.4VulDB
6.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:O/RC:C2.83.4VulDB
6.3CVSS 3.0MediumCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:O/RC:C2.83.4VulDB
5.3CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P——VulDB

Vulnerability scoring details

Base CVSS 4.0 score

5.3Medium
CVSS 4.0 vector shape for CVE-2024-14043Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineVulDB

    Advisory disclosed

  2. Source timelineVulDB

    VulDB entry created

  3. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  4. Source timelineVulDB

    VulDB entry last update

  5. CVE publishedCVE Program

    The CVE record was published.

  6. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aOpen5GS2.7.0, 2.7.1, 2.7.2Listed
Weakness

CWE details

CWE-119CWE-122

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