Unauthenticated AMF crash via missing gNB identifier
Published Nov 12, 2025 · Updated Nov 13, 2025
Denial of service in free5GC 4.1.0 and earlier allows remote attackers to crash the AMF via a crafted NGAP message. The handleUplinkRANConfigurationTransferMain function dereferences an absent gNB identifier instead of rejecting the malformed message. A gNB connection to the AMF NGAP interface is required; one malformed message triggers a nil-pointer panic that stops the AMF process.
Summary
What happened
Denial of service in free5GC 4.1.0 and earlier allows remote attackers to crash the AMF via a crafted NGAP message. The handleUplinkRANConfigurationTransferMain function dereferences an absent gNB identifier instead of rejecting the malformed message. A gNB connection to the AMF NGAP interface is required; one malformed message triggers a nil-pointer panic that stops the AMF process.
The record
- CVE
- CVE-2025-63679
- Published
- Nov 12, 2025
- Updated
- Nov 13, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 12, 2025CVE publishedPublication date reported by the CVE source.
- Nov 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- UplinkRANConfigurationTransfer crash packet captureproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo