dbcve.org
NULL Pointer DereferenceWeakness · CWE-476

CVE-2024-24446

MEDIUM · 6.5 CVSS v3.1 Published 2024-11-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
An uninitialized pointer dereference in OpenAirInterface CN5G AMF up to v2.0.0 allows attackers to cause a Denial of Service (DoS) via a crafted InitialContextSetupResponse message sent to the AMF.

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 confidence

An uninitialized pointer dereference in the OpenAirInterface CN5G AMF (Access and Mobility Management Function) up to version v2.0.0 allows attackers to crash the AMF via a specially crafted InitialContextSetupResponse message, causing a Denial of Service.

MitigationUpgrade the AMF to a version beyond v2.0.0 that includes proper pointer initialization, or apply vendor-provided patches. Network segmentation can limit exposure to unauthorized 5G signaling traffic.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenAirInterface AMF installation
    Look for AMF processes, containers, or installation directories. Common paths include /openair-amf, or look for processes named 'amf' in container orchestration systems.
    Affected if OpenAirInterface AMF is deployed in the environment
  2. Determine installed AMF version
    Check the version via container image tag, binary version flag (--version), or version file in the installation directory.
    Affected if Version is v2.0.0 or lower (including unversioned builds from before the fix)
  3. Verify AMF network exposure
    Review network configuration, exposed ports (typically UDP/38412 for N2 interface), and firewall rules to determine if the AMF can receive 5G signaling from untrusted sources.
    Affected if The N2 interface (InitialContextSetupResponse messages) is accessible from networks outside the trusted 5G core infrastructure
  4. Check for crash logs
    Search AMF application logs and system logs (journalctl, /var/log/syslog) for segfaults, null pointer dereferences, or crashes occurring when processing N2 messages.
    Affected if Recent AMF crashes match the pattern of uninitialized pointer dereference during InitialContextSetupResponse handling

A user is affected if they have OpenAirInterface AMF at version v2.0.0 or below that is exposed to 5G N2 signaling traffic, or if they observe crashes consistent with this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the AMF to a version beyond v2.0.0 that includes proper pointer initialization, or apply vendor-provided patches. Network segmentation can limit exposure to unauthorized 5G signaling traffic.

Recommended fix Moderate confidence

v2.0.1 or later stable release from openairinterface.org

  1. 1. Identify the current OpenAirInterface CN5G AMF version in use by checking the deployed software or build configuration
  2. 2. Obtain the latest stable release from the official OpenAirInterface repository (openairinterface.org) or release notes
  3. 3. Review the release notes for v2.0.1 or later versions to confirm the NULL pointer dereference vulnerability is addressed
  4. 4. Before upgrading, review the AMF configuration and ensure compatibility with the target release
  5. 5. Perform the upgrade in a test/staging environment first to validate functionality
  6. 6. After successful testing, schedule a maintenance window and deploy the upgrade to production
  7. 7. Monitor the AMF logs after upgrade to ensure the vulnerability is remediated and no new issues appear
Caveat Review release notes for any configuration or API changes between v2.0.0 and the target release; some parameters may have been renamed or behavior changed

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24446 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-24446 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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