Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-63679: n/a

0
Critical
VulnerabilityCVE-2025-63679cvecve-2025-63679
Published: Wed Nov 12 2025 (11/12/2025, 00:00:00 UTC)
Source: CVE Database V5

Description

free5gc v4.1.0 and before is vulnerable to Buffer Overflow. When AMF receives an UplinkRANConfigurationTransfer NGAP message from a gNB, the AMF process crashes.

AI-Powered Analysis

AILast updated: 11/19/2025, 19:43:27 UTC

Technical Analysis

CVE-2025-63679 is a buffer overflow vulnerability identified in free5gc, an open-source 5G core network implementation, specifically affecting version 4.1.0 and earlier. The vulnerability arises when the AMF component receives a specially crafted UplinkRANConfigurationTransfer message via the NG Application Protocol (NGAP) from a gNB (next-generation NodeB). Due to improper bounds checking or insufficient validation of the message payload, the AMF process crashes, leading to a denial of service. Given the critical CVSS score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), the vulnerability can be exploited remotely over the network without any authentication or user interaction, resulting in complete compromise of confidentiality, integrity, and availability of the AMF service. The AMF is a pivotal element in the 5G core, responsible for mobility management and session handling, so its disruption can severely impact network operations. Although no public exploits are currently known, the nature of the vulnerability (CWE-120: classic buffer overflow) suggests potential for remote code execution if exploited skillfully. The lack of available patches at the time of disclosure increases urgency for operators to implement interim mitigations. This vulnerability highlights risks inherent in open-source 5G core deployments, which are increasingly adopted for flexibility and cost reasons but require rigorous security validation. Organizations must scrutinize NGAP message handling and consider network segmentation and anomaly detection to mitigate exploitation risks until patches are released.

Potential Impact

For European organizations, especially telecom operators and infrastructure providers deploying free5gc or similar open-source 5G core solutions, this vulnerability poses a significant threat. Exploitation can cause AMF process crashes, leading to denial of service and disruption of 5G network services, impacting millions of users and critical communications. The potential for remote code execution could allow attackers to gain control over core network functions, compromising subscriber data confidentiality and network integrity. This could affect emergency services, enterprise connectivity, and consumer mobile services, resulting in financial losses, reputational damage, and regulatory penalties under GDPR and telecom regulations. The disruption of 5G services could also impact industries relying on 5G connectivity such as manufacturing, transportation, and healthcare. Given the critical role of 5G in European digital infrastructure and the strategic push for 5G adoption, this vulnerability represents a high operational and security risk.

Mitigation Recommendations

1. Immediate monitoring of NGAP traffic to detect anomalous or malformed UplinkRANConfigurationTransfer messages using deep packet inspection or protocol-aware IDS/IPS systems. 2. Implement network segmentation to isolate the AMF and other core network functions from untrusted networks and limit exposure to potentially malicious gNBs. 3. Apply strict input validation and rate limiting on NGAP messages at the network edge or within the AMF if possible. 4. Engage with free5gc maintainers and security communities to obtain patches or security updates as soon as they become available. 5. Conduct thorough code audits and fuzz testing on NGAP message handling components to identify and remediate similar vulnerabilities proactively. 6. Develop incident response plans specifically for 5G core network disruptions, including fallback procedures and rapid recovery mechanisms. 7. Consider deploying additional security controls such as runtime application self-protection (RASP) or memory protection techniques to mitigate buffer overflow exploitation. 8. Collaborate with telecom vendors and regulators to share threat intelligence and coordinate defensive measures.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-10-27T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 6914d9d9789e20b80072146f

Added to database: 11/12/2025, 7:02:49 PM

Last enriched: 11/19/2025, 7:43:27 PM

Last updated: 11/20/2025, 8:47:27 AM

Views: 24

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats