# CVE-2024-12169: Denial of service in RTU500

> An attacker can restart the RTU500 controlled station via a specific attack sequence when secure communication is enabled, causing denial of service.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/R:A`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Mar 2025
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-6pf8-q335-vxv9

## What is CVE-2024-12169?

CVE-2024-12169 is a high-severity denial of service vulnerability in Hitachi Energy RTU500, published on 25 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability exists in RTU500 IEC 60870-5-104 controlled station functionality and IEC 61850 functionality, that allows an attacker performing a specific attack sequence to restart the affected CMU. This vulnerability only applies, if secure communication using IEC 62351-3 (TLS) is enabled.

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


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

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

## Is CVE-2024-12169 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-12169 is a high-severity denial of service vulnerability in Hitachi Energy RTU500, published on 25 Mar 2025. 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-12169 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-12169/ (Markdown: https://insights.sbomify.com/CVE-2024-12169/index.md)
```

## Sources

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

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