# CVE-2024-24446: Null dereference in n/a

> Attackers can cause a Denial of Service in OpenAirInterface CN5G AMF by sending a crafted InitialContextSetupResponse message due to an uninitialized pointer dereference.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Nov 2024
- **Updated:** 19 Nov 2024
- **Also known as:** GHSA-8vpp-w76f-8mx8

## What is CVE-2024-24446?

CVE-2024-24446 is a medium-severity vulnerability in n/a, published on 15 Nov 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2024-24446?


## How do I fix CVE-2024-24446?

No fix has been published for CVE-2024-24446 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-24446 being exploited?

There is no known exploitation of CVE-2024-24446 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-24446 and fix it if it is affected.

What it is: CVE-2024-24446 is a medium-severity vulnerability in n/a, published on 15 Nov 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-24446 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-24446/ (Markdown: https://insights.sbomify.com/CVE-2024-24446/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-24446
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-24446
- OSV: https://osv.dev/vulnerability/CVE-2024-24446

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-24446/
Summaries are generated and may contain mistakes; the official description above is the record.