Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2024-24450: Stack-based buffer overflow in OpenAirInterface CN5G AMF ngap_handle_pdu_session_resource_setup_response

Published Nov 15, 2024 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.3Medium · v3.1
EPSS1.5%74th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2024-24450CWE-121

CVE-2024-24450 is a stack-based buffer overflow in OpenAirInterface CN5G AMF versions up to and including 2.0.0. The flaw is in the ngap_handle_pdu_session_resource_setup_response routine, where a memcpy operation can overflow a stack buffer when processing a PDU Session Resource Setup Response containing a sufficiently large FailedToSetupList information element (IE). An attacker with access to the N2 interface can trigger the vulnerable code path by sending a crafted NGAP message, causing memory corruption in the AMF process. The reported impact includes denial of service and potential code execution.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can crash the AMF, resulting in denial of service for 5G core control-plane functions handled by the affected component. Because the vulnerability is a stack-based buffer overflow caused by an unchecked memcpy, exploitation may also permit arbitrary code execution in the AMF process context, depending on exploitability conditions such as memory layout, compiler protections, and runtime environment.

Mitigation

If you can’t patch tonight, do this now.

Restrict and tightly control access to the N2 interface so that only authorized and expected RAN components can communicate with the AMF. Use network segmentation, ACLs, and filtering to prevent untrusted systems from sending NGAP traffic to the AMF. Monitor the AMF for malformed or anomalously large PDU Session Resource Setup Response messages and crashes associated with NGAP processing. Where feasible, deploy compiler and runtime hardening protections and isolate the AMF process to reduce the impact of a successful overflow until a fixed version is installed.

Remediation

Patch, then assume compromise.

Upgrade OpenAirInterface CN5G AMF to a version newer than 2.0.0 that fixes the bounds-checking flaw in ngap_handle_pdu_session_resource_setup_response. The vulnerable memcpy handling of the FailedToSetupList IE should be corrected by validating the size of attacker-controlled input before copying it into stack-allocated memory. If a vendor or project patch is available, apply it promptly and redeploy the AMF component.

FAQ

Frequently asked questions

Is CVE-2024-24450 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2024-24450 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2024-24450?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2024-24450, the earliest disclosed Mar 13, 2025.
Is there a patch for CVE-2024-24450?
Upgrade OpenAirInterface CN5G AMF to a version newer than 2.0.0 that fixes the bounds-checking flaw in ngap_handle_pdu_session_resource_setup_response. The vulnerable memcpy handling of the FailedToSetupList IE should be corrected by validating the size of attacker-controlled input before copying it into stack-allocated memory.
How severe is CVE-2024-24450?
CVE-2024-24450 has a CVSS v3.1 score of 5.3 (Medium) and an EPSS score of 1.5% (74th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.