CVE-2024-2617

HIGHNVD 7.27.2—

7.2

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.

CVSS v3: 7.2
EG Score: 7.2(medium)
EPSS: 7.3%
KEV: Not listed

Published

April 30, 2024

Last Modified

April 15, 2026

References (2)

cybersecurity@hitachienergyhttps://publisher.hitachienergy.com/preview?DocumentId=8DBD000199&languageCode=en&Preview=true
af854a3a-2127-422b-91ae-364da2661108https://publisher.hitachienergy.com/preview?DocumentId=8DBD000199&languageCode=en&Preview=true

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-358Improperly Implemented Security Check for Standard

Data Freshness Timeline

(refreshed 14× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:12 UTCepss_batch
2026-06-02 20:12 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-26 07:18 UTCepss_batch

Frequently asked(5)

What is CVE-2024-2617?

CVE-2024-2617 is a high vulnerability published on April 30, 2024. 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…

When was CVE-2024-2617 disclosed?

CVE-2024-2617 was first published in the National Vulnerability Database on April 30, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2024-2617 actively exploited?

CVE-2024-2617 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2024-2617?

CVE-2024-2617 has a CVSS v3 base score of 7.2 (NVD).

How do I remediate CVE-2024-2617?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-2617, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-2617

Explore →

Is Your Infrastructure Affected by CVE-2024-2617?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2024-2617

📅 Published

🔄 Last Modified

🔗 References (2)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2024-2617?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (2)

Frequently asked(5)

Related CVEs(same CWE)