# CVE-2022-29492: Denial of service in MicroSCADA Pro SYS600

> Attackers can cause denial of service in Hitachi Energy MicroSCADA systems by sending malformed IEC 104 TCP packets that leave connections open.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2022
- **Updated:** 4 Jun 2025
- **Also known as:** GHSA-j6fw-8c2x-xmgq

## What is CVE-2022-29492?

CVE-2022-29492 is a medium-severity denial of service vulnerability in Hitachi Energy MicroSCADA Pro SYS600, published on 14 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Input Validation vulnerability in the handling of a malformed IEC 104 TCP packet in the Hitachi Energy MicroSCADA X SYS600, MicroSCADA Pro SYS600. Upon receiving a malformed IEC 104 TCP packet, the malformed packet is dropped, however the TCP connection is left open. This may cause a denial-of-service if the affected connection is left open. This issue affects: Hitachi Energy MicroSCADA Pro SYS600 version 9.4 FP2 Hotfix 4 and earlier versions Hitachi Energy MicroSCADA X SYS600 version 10 to version 10.3.1. cpe:2.3:a:hitachienergy:microscada_pro_sys600:9.0:*:*:*:*:*:*:* cpe:2.3:a:hitachienergy:microscada_pro_sys600:9.1:*:*:*:*:*:*:* cpe:2.3:a:hitachienergy:microscada_pro_sys600:9.2:*:*:*:*:*:*:* cpe:2.3:a:hitachienergy:microscada_pro_sys600:9.3:*:*:*:*:*:*:* cpe:2.3:a:hitachienergy:microscada_pro_sys600:9.4:*:*:*:*:*:*:* cpe:2.3:a:hitachienergy:microscada_x_sys600:10:*:*:*:*:*:*:* cpe:2.3:a:hitachienergy:microscada_x_sys600:10.1:*:*:*:*:*:*:* cpe:2.3:a:hitachienergy:microscada_x_sys600:10.1.1:*:*:*:*:*:*:* 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:*:*:*:*:*:*:*

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Hitachienergy Microscada X Sys600.

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

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

## Is CVE-2022-29492 being exploited?

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

## Other vulnerabilities in Hitachi Energy MicroSCADA Pro SYS600

- [CVE-2026-9853](https://insights.sbomify.com/CVE-2026-9853/): Missing authorization in MicroSCADA SYS600 (high 8.5)
- [CVE-2026-9854](https://insights.sbomify.com/CVE-2026-9854/): Privilege escalation in MicroSCADA SYS600 (high 8.5)
- [CVE-2025-39204](https://insights.sbomify.com/CVE-2025-39204/): Information disclosure in MicroSCADA X SYS600 (high 8.5)
- [CVE-2022-29490](https://insights.sbomify.com/CVE-2022-29490/): Missing authorization in MicroSCADA X SYS600 (high 8.5)
- [CVE-2025-39202](https://insights.sbomify.com/CVE-2025-39202/): Missing authorization in MicroSCADA X SYS600 (high 8.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29492 is a medium-severity denial of service vulnerability in Hitachi Energy MicroSCADA Pro SYS600, published on 14 Sep 2022. 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-29492 in the wild and no public exploit code.

Affected product: Hitachi Energy MicroSCADA Pro SYS600. 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-29492/ (Markdown: https://insights.sbomify.com/CVE-2022-29492/index.md)
```

## Sources

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

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