CVE-2024-2617 json
A vulnerability exists in the RTU500 that allows for authenticated and authorized users to bypass secure update, if secure update feature w…
published 2024-04-30 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-27566
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 52%
- public exploits
- 0
- none known
Summary
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.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-25-023-02 updated cvss 7.2
Hitachi Energy RTU500 Series Product (Update B)
-
Hitachi Energy RTU500 series CMU Firmware vers:RTU500_series_CMU_Firmware/>=13.2.1, <=13.2.7, vers:RTU500_series_CMU_Firmware/>=13.4.1, <=13.4.4, vers:RTU500_series_CMU_Firmware/>=13.5.1, <=13.5.3affected: vendor fix
Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
0.67% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Hitachi Energy RTU500 series CMU firmware
- hitachienergy rtu500_firmware
Classification
- Weakness
-
- CWE-358 Improperly Implemented Security Check for Standard
References
Sources
- CVE List CVE-2024-2617
- NVD CVE-2024-2617
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.