# CVE-2024-11499: Null dereference in RTU500

> An authenticated attacker can cause a denial of service by triggering a null dereference during certificate updates on active connections.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/R:A`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Mar 2025
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-h77r-2p45-qp9h

## What is CVE-2024-11499?

CVE-2024-11499 is a medium-severity vulnerability in Hitachi Energy RTU500, published on 25 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability exists in RTU500 IEC 60870-4-104 controlled station functionality, that allows an authenticated and authorized attacker to perform a CMU restart. The vulnerability can be triggered if certificates are updated while in use on active connections.

The affected CMU will automatically recover itself if an attacker successfully exploits this vulnerability.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

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

## Is CVE-2024-11499 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-11499 is a medium-severity vulnerability in Hitachi Energy RTU500, published on 25 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-11499 in the wild and no public exploit code.

Affected product: Hitachi Energy RTU500. 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-11499/ (Markdown: https://insights.sbomify.com/CVE-2024-11499/index.md)
```

## Sources

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

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