# CVE-2022-3353: IEC 61850 MMS-Server Vulnerability in multiple Hitachi Energy Products

> An attacker can cause the IEC 61850 MMS-server to stop accepting new connections, disrupting industrial control system communications.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Feb 2023
- **Updated:** 12 Mar 2025
- **Also known as:** GHSA-r27w-hfm7-9mc2

## What is CVE-2022-3353?

CVE-2022-3353 is a medium-severity denial of service vulnerability in Hitachi Energy FOX61x TEGO1, published on 21 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability exists in the IEC 61850 communication stack that affects multiple Hitachi Energy products. 

An attacker could exploit the vulnerability by using a specially crafted message sequence, to force the IEC 61850 MMS-server communication stack, to stop accepting new MMS-client connections. 

Already existing/established client-server connections are not affected.

List of affected CPEs:

  *  cpe:2.3:o:hitachienergy:fox61x_tego1:r15b08:*:*:*:*:*:*:*
  *  cpe:2.3:o:hitachienergy:fox61x_tego1:r2a16_3:*:*:*:*:*:*:*
  *  cpe:2.3:o:hitachienergy:fox61x_tego1:r2a16:*:*:*:*:*:*:*
  *  cpe:2.3:o:hitachienergy:fox61x_tego1:r1e01:*:*:*:*:*:*:*
  *  cpe:2.3:o:hitachienergy:fox61x_tego1:r1d02:*:*:*:*:*:*:*
  *  cpe:2.3:o:hitachienergy:fox61x_tego1:r1c07:*:*:*:*:*:*:*
  *  cpe:2.3:o:hitachienergy:fox61x_tego1:r1b02:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:gms600:1.3.0:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.1.*:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.5.*:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.6.0:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.6.0.1:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.7.0:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.7.2:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:itt600_sa_explorer:1.8.0:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.0.*:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.1.0.4:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:itt600_sa_explorer:2.1.0.5:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:microscada_x_sys600:10:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:microscada_x_sys600:10.*:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:microscada_x_sys600:10.2:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:microscada_x_sys600:10.2.1:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:microscada_x_sys600:10.3:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:microscada_x_sys600:10.3.1:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:microscada_x_sys600:10.4:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:microscada_x_sys600:10.4.1:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:mms:2.2.3:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:pwc600:1.0:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:pwc600:1.1:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:pwc600:1.2:*:*:*:*:*:*:*
  *  cpe:2.3:o:hitachienergy:reb500:7:*:*:*:*:*:*:*:*
  *  cpe:2.3:o:hitachienergy:reb500:8:*:*:*:*:*:*:*
  *  cpe:2.3:o:hitachienergy:relion670:1.2.*:*:*:*:*:*:*:*
  *  cpe:2.3:o:hitachienergy:relion670:2.0.*:*:*:*:*:*:*:*
  *  cpe:2.3:o:hitachienergy:relion650:1.1.*:*:*:*:*:*:*:*
  *  cpe:2.3:o:hitachienergy:relion650:1.3.*:*:*:*:*:*:*:*
  *  cpe:2.3:o:hitachienergy:relion650:2.1.*:*:*:*:*:*:*:*
  *  cpe:2.3:o:hitachienergy:relion670:2.1.*:*:*:*:*:*:*:*
  *  cpe:2.3:o:hitachienergy:relionSAM600-IO:2.2.1:*:*:*:*:*:*:*
  *  cpe:2.3:o:hitachienergy:relionSAM600-IO:2.2.5:*:*:*:*:*:*:*
  *  cpe:2.3:o:hitachienergy:relion670:2.2.*:*:*:*:*:*:*:*
  *  cpe:2.3:o:hitachienergy:relion650:2.2.*:*:*:*:*:*:*:*
  *  cpe:2.3:o:hitachienergy:rtu500cmu:12.*.*:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:rtu500cmu:13.*.*:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:txpert_hub_coretec_4:2.*:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:txpert_hub_coretec_4:3.0:*:*:*:*:*:*:*
  *  cpe:2.3:a:hitachienergy:txpert_hub_coretec_5:3.0:*:*:*:*:*:*:*

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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

It affects 13 products.


Products: Hitachienergy Fox615 Tego1 Firmware, Hitachienergy Gms600 Firmware, Hitachienergy Itt600 Sa Explorer, Hitachienergy Modular Switchgear Monitoring Firmware, Hitachienergy Pwc600 Firmware, Hitachienergy Reb500 Firmware, Hitachienergy Relion 650 Firmware, Hitachienergy Relion 670 Firmware, Hitachienergy Relion Sam600-Io Firmware, Hitachienergy Rtu500 Firmware, Hitachienergy Sys600 Firmware, Hitachienergy Txpert Hub Coretec 4 Firmware, Hitachienergy Txpert Hub Coretec 5 Firmware.

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

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

## Is CVE-2022-3353 being exploited?

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

## Other vulnerabilities in Hitachi Energy FOX61x TEGO1

- [CVE-2021-27196](https://insights.sbomify.com/CVE-2021-27196/): Specially Crafted IEC 61850 Protocol Sequence Vulnerability (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3353 is a medium-severity denial of service vulnerability in Hitachi Energy FOX61x TEGO1, published on 21 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-3353 in the wild and no public exploit code.

Affected product: Hitachi Energy FOX61x TEGO1. 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-3353/ (Markdown: https://insights.sbomify.com/CVE-2022-3353/index.md)
```

## Sources

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

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