Hitachi Energy Relion RSA timing side-channel in OpenSSL
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.
CVE-2022-4304 timing attack in OpenSSL affects Hitachi Energy Relion 670, 650, SAM600-IO; decrypt TLS traffic via RSA decryption timing.
Hitachi Energy has published a security advisory addressing CVE-2022-4304, a timing-based side-channel vulnerability in the OpenSSL RSA decryption implementation affecting multiple versions of the Relion 670, 650, and SAM600-IO series. This is a Bleichenbacher-style attack that exploits timing differences in RSA decryption across all padding modes (PKCS#1 v1.5, RSA-OEAP, RSA-SVE). An attacker with network access to observed TLS connections can send a large number of trial decryption messages to the affected device, record processing times, and use the timing patterns to recover the pre-master secret, allowing decryption of previously captured TLS application data.
The vulnerability affects Relion 670/650 series version 2.2.0 (all revisions), versions 2.2.1 through 2.2.1.8, 2.2.2 through 2.2.2.5, 2.2.3 through 2.2.3.6, 2.2.4 through 2.2.4.3, and Relion 670/650/SAM600-IO series version 2.2.5 through 2.2.5.5. Hitachi Energy has released patched versions (2.2.1.9, 2.2.2.6, 2.2.3.7, 2.2.4.4, 2.2.5.6 and later) that remediate the issue.
Defenders managing these critical infrastructure protection devices should prioritize updating to the latest patched versions, isolate affected systems from direct internet exposure, restrict network access to TLS endpoints, and implement monitoring for anomalous connection patterns or timing-based scanning attempts.
Mentioned in this report
Source reporting: https://www.cisa.gov/news-events/ics-advisories/icsa-25-160-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