VORANT. Threat Intelligence Research Sign in Create a free account

Hitachi Energy Relion 670/650/SAM600-IO IEC 61850 input validation flaw

routine vulnerability energyinfrastructure

Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.

Input validation flaw in IEC 61850 GOOSE message handling causes device reboot in Hitachi Energy Relion series.

Hitachi Energy has published a security advisory for CVE-2023-4518 affecting the Relion 670, Relion 670/650, and Relion 670/650/SAM600-IO series devices used in energy infrastructure. The vulnerability exists in improper input validation of IEC 61850 GOOSE (Generic Object Oriented Substation Event) messages. An attacker who sends specially crafted out-of-range values in GOOSE messages to a device with GOOSE receiving blocks configured can cause the affected device to reboot, resulting in operational disruption. The vulnerability requires the device to have GOOSE receiving capabilities enabled; exploitation is not remote unauthenticated but requires network access to the control system.

Multiple versions across the product line are affected, spanning versions 2.0.0.0 through 2.2.5.x. Hitachi Energy has released patched versions for all affected product lines, with remediation available in versions 2.0.0.14, 2.1.0.6, 2.2.1.9, 2.2.2.6, 2.2.3.7, 2.2.4.4, and 2.2.5.6. Organizations operating Relion devices should update to the recommended patched versions and apply network segmentation controls appropriate for critical energy infrastructure, ensuring these devices are not directly accessible from untrusted networks.

Mentioned in this report

Vulnerabilities CVE-2023-4518

Source reporting: https://www.cisa.gov/news-events/ics-advisories/icsa-25-133-02

What this brief leaves out

This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.

It sits in a corpus of 13,854 reports from 146 sources, 614 of them written in the last seven days, and it grows through the day.

A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.

Create a free account   What it costs