# CVE-2024-2617: Security feature bypass in RTU500 series CMU firmware

> Authenticated users can bypass secure update mechanisms to install unsigned firmware on RTU500 devices if the feature is not enabled on all CMUs.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Apr 2024
- **Updated:** 4 Mar 2026
- **Also known as:** GHSA-8rv2-8c5x-g54v

## What is CVE-2024-2617?

CVE-2024-2617 is a high-severity vulnerability in Hitachi Energy RTU500 series CMU firmware, published on 30 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability exists in the RTU500 that allows for authenticated and authorized users to bypass secure update, 

if secure update feature was not enabled on all
CMUs of a RTU500. If a
malicious actor successfully exploits this vulnerability, they
could use it to update the RTU500 with unsigned firmware.

Weakness: CWE-358 (Improperly Implemented Security Check for Standard)

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


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

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

## Is CVE-2024-2617 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-2617 is a high-severity vulnerability in Hitachi Energy RTU500 series CMU firmware, published on 30 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-2617 in the wild and no public exploit code.

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

## Sources

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

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