CVE-2024-24450
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedStack-based memcpy buffer overflow in the ngap_handle_pdu_session_resource_setup_response routine in OpenAirInterface CN5G AMF <= 2.0.0 allows a remote attacker with access to the N2 interface to carry out denial of service against the AMF and potentially execute code by sending a PDU Session Resource Setup Response with a suffciently large FailedToSetupList IE.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStack-based buffer overflow in the NGAP PDU Session Resource Setup Response handler (ngap_handle_pdu_session_resource_setup_response) in OpenAirInterface 5G AMF <= 2.0.0. A remote attacker with N2 interface access can send a PDU Session Resource Setup Response containing an oversized FailedToSetupList IE, causing memcpy to write beyond stack buffer boundaries, leading to denial of service and potential code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm OpenAirInterface 5G AMF is installedIdentify if OpenAirInterface AMF software is running on the system. Look for AMF processes, configuration files, or service logs indicating the presence of the OpenAirInterface 5G core network function.Affected if OpenAirInterface 5G AMF is present on the system
-
Check AMF versionDetermine the installed AMF version by examining version strings in binaries, container labels, RPM/Debian package metadata, or the output of 'amf --version' if available. Compare against the affected range: any version <= 2.0.0.Affected if The installed AMF version is 2.0.0 or any earlier version
-
Verify N2 interface exposureInspect network configuration and firewall rules to determine if the N2 interface (SCTP port 38462 by default for 3GPP N2) is accessible from untrusted network segments. Check AMF configuration files for bind addresses and accepted peer nodes.Affected if The N2 interface is exposed to networks or hosts outside the trusted 5G gNB deployment
-
Confirm PDU Session Resource Setup is enabledCheck AMF configuration to verify that PDU Session management is enabled. Look for related configuration flags or logs indicating PDU Session Resource Setup Response messages are being processed.Affected if PDU Session functionality is enabled and the AMF processes PDU Session Resource Setup Response messages from gNB nodes
The environment is affected if OpenAirInterface 5G AMF version 2.0.0 or earlier is running with PDU Session enabled and the N2 interface is accessible to untrusted actors, allowing them to send malicious oversized FailedToSetupList IEs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement bounds checking on the FailedToSetupList IE length before the memcpy operation in the vulnerable routine, or upgrade to a patched version if available. Restrict N2 interface access to trusted 5G gNB nodes.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24450 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-24450 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data