CVE-2024-24445
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 · uneditedOpenAirInterface CN5G AMF (oai-cn5g-amf) <= 2.0.0 contains a null dereference in its handling of unsupported NGAP protocol messages which allows an attacker with network-adjacent access to the AMF to carry out denial of service. When a procedure code/presence field tuple is received that is unsupported, OAI indexes into a null function pointer and subsequently dereferences it.
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 confidenceOpenAirInterface CN5G AMF contains a null pointer dereference vulnerability in its NGAP protocol message handling. When the AMF receives an unsupported procedure code/presence field tuple, it indexes into a null function pointer and dereferences it, causing a denial of service. An attacker with network-adjacent access can trigger this condition remotely.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/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.
-
Identify if OpenAirInterface CN5G AMF is deployedSearch for oai-cn5g-amf process or check for its installation path, commonly found under /openair-amf or via systemctl status oai-amfAffected if The oai-cn5g-amf service or binary is present in the environment
-
Determine the installed AMF versionRun 'oai-amf --version' or check the version through the package manager, or inspect the binary metadataAffected if The version is lower than 2.0.0 or cannot be determined (unknown versions should be treated as vulnerable)
-
Verify NGAP service is exposedCheck the AMF configuration file (typically amf.conf) for 'ngapIp' binding to external interfaces, or use netstat/ss to see if port 38412/SCTP is listening on non-loopback addressesAffected if The NGAP service listens on interfaces accessible to network-adjacent attackers (0.0.0.0 or non-trusted IP addresses)
-
Review AMF logs for crash indicatorsExamine logs under /var/log/oai/amf*.log or the journal (journalctl -u oai-amf) for 'null pointer', 'segfault', or 'NGAP' error messagesAffected if Recent crashes or null pointer dereference errors related to NGAP message handling are present in logs
The environment is affected if OpenAirInterface CN5G AMF is running with a version below 2.0.0 and its NGAP interface is accessible to untrusted network segments.
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 oai-cn5g-amf to a version beyond 2.0.0 that includes the patch for this vulnerability. If immediate upgrade is not possible, restrict network access to the AMF to trusted 5G network elements to reduce attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24445 — 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-24445 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