# CVE-2022-3864: Security feature bypass in Relion 670/650/SAM600-IO Series

> An attacker with privileged access can bypass signature validation to install a tampered update, causing a temporary denial of service on Hitachi Energy Relion IEDs.

- **Severity:** Medium 4.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Jan 2024
- **Updated:** 27 Aug 2024
- **Also known as:** GHSA-5pj9-g7qw-3qwv

## What is CVE-2022-3864?

CVE-2022-3864 is a medium-severity vulnerability in Hitachi Energy Relion 670/650/SAM600-IO Series, published on 4 Jan 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A vulnerability exists in the Relion update package signature validation. A tampered update package could cause the IED to restart. After restart the device is back to normal operation.
An attacker could exploit the vulnerability by first gaining access to
the system with security privileges and attempt to update the IED
with a malicious update package. Successful exploitation of this
vulnerability will cause the IED to restart, causing a temporary Denial of Service.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2022-3864?

It affects 3 products.


Products: Hitachienergy Relion 650 Firmware, Hitachienergy Relion 670 Firmware, Hitachienergy Relion Sam600-Io Firmware.

## How do I fix CVE-2022-3864?

No fix has been published for CVE-2022-3864 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-3864 being exploited?

There is no known exploitation of CVE-2022-3864 in the wild and no public exploit code.

## Other vulnerabilities in Hitachi Energy Relion 670/650/SAM600-IO Series

- [CVE-2021-35535](https://insights.sbomify.com/CVE-2021-35535/): Insufficient Security Control Vulnerability (high 8.1)
- [CVE-2019-18247](https://insights.sbomify.com/CVE-2019-18247/): Denial of service in Relion 650 and 670 Series (high 7.5)
- [CVE-2023-4518](https://insights.sbomify.com/CVE-2023-4518/): Denial of service in Relion670 (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3864 and fix it if it is affected.

What it is: CVE-2022-3864 is a medium-severity vulnerability in Hitachi Energy Relion 670/650/SAM600-IO Series, published on 4 Jan 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-3864 in the wild and no public exploit code.

Affected product: Hitachi Energy Relion 670/650/SAM600-IO Series. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-3864/ (Markdown: https://insights.sbomify.com/CVE-2022-3864/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-3864
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-3864
- OSV: https://osv.dev/vulnerability/CVE-2022-3864

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-3864/
Summaries are generated and may contain mistakes; the official description above is the record.