# CVE-2024-24453: Denial of service in HPE Athonet Core

> Attackers can cause a Denial of Service in the cellular network by sending crafted payloads to the HPE Athonet Core MME.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 15 Nov 2024
- **Updated:** 26 Aug 2025
- **Also known as:** GHSA-qf7p-2hmj-48mq

## What is CVE-2024-24453?

CVE-2024-24453 is a medium-severity denial of service vulnerability in Hewlett Packard Enterprise (HPE) HPE Athonet Core, published on 15 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An invalid memory access when handling the ProtocolIE_ID field of E-RAB NotToBeModifiedBearerModInd information element in Athonet vEPC MME v11.4.0 allows attackers to cause a Denial of Service (DoS) to the cellular network by repeatedly initiating connections and sending a crafted payload.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2024-24453 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-24453 is a medium-severity denial of service vulnerability in Hewlett Packard Enterprise (HPE) HPE Athonet Core, published on 15 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-24453 in the wild and no public exploit code.

Affected product: Hewlett Packard Enterprise (HPE) HPE Athonet Core. 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-24453/ (Markdown: https://insights.sbomify.com/CVE-2024-24453/index.md)
```

## Sources

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

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