CVE-2024-24443
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 · uneditedAn uninitialized pointer dereference in the ngap_handle_pdu_session_resource_setup_response routine of OpenAirInterface CN5G AMF (oai-cn5g-amf) up to v2.0.0 allows attackers to cause a Denial of Service (DoS) via a crafted PDU Session Resource Setup Response.
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 · moderate confidenceAn uninitialized pointer dereference in the ngap_handle_pdu_session_resource_setup_response function of the OpenAirInterface 5G Core AMF allows remote attackers to cause a denial of service by sending a crafted PDU Session Resource Setup Response message.
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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Identify OpenAirInterface AMF installationLocate the AMF binary or service on the system. Common paths include /usr/local/bin/amf, /opt/oai/amf, or check running processes for 'amf' or 'openairinterface-amf'. Use commands like 'ps aux | grep -i amf' or 'which amf'.Affected if OpenAirInterface AMF is not found on the system (not affected).
-
Determine installed AMF versionRun the AMF binary with a version flag, such as 'amf --version' or check the git commit/version information in the installation directory. If installed via package manager, use 'dpkg -l' or 'rpm -qa' to query the oai-amf package.Affected if The installed version is prior to v2.0.1 (e.g., v1.x.x, v2.0.0) and the patch has not been applied.
-
Verify NGAP protocol handler is activeExamine AMF configuration files (typically amf.conf or similar in /etc/oai or /opt/oai/conf) for 'ngap' or 'N2' interface configuration. Check if the NGAP listener is bound to a port (often port 38412). Use 'netstat -tulpn | grep amf' or 'ss -tulpn | grep 38412' to confirm the NGAP interface is listening.Affected if The NGAP interface is enabled and the AMF is listening for N2 connections from gNB nodes.
-
Confirm PDU Session Resource handling is configuredReview the AMF configuration for 'pdu-session' or 'session-management' related settings. In the configuration files, look for entries enabling PDU Session Resource Setup Request handling. This feature is typically enabled by default for 5G core operation.Affected if PDU Session Resource management is enabled in the AMF configuration, which is the default operational state for 5G AMF.
The environment is affected if OpenAirInterface CN5G AMF is running with a version prior to v2.0.1, the NGAP interface is enabled, and PDU Session Resource handling is active (which is the default configuration for operational 5G cores).
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 dataUpgrade to a patched version of OpenAirInterface CN5G AMF (v2.0.1 or later) or apply vendor-provided patches to properly initialize the pointer in the NGAP handler before use.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24443 — 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-24443 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