# CVE-2022-3388: Input Validation Vulnerability in Hitachi Energy’s MicroSCADA Pro/X SYS600 Products


- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Nov 2022
- **Updated:** 23 Jul 2025
- **Also known as:** GHSA-5xm5-wrvq-pc6h

## What is CVE-2022-3388?

CVE-2022-3388 is a high-severity vulnerability in Hitachi Energy MicroSCADA Pro SYS600, published on 21 Nov 2022. 

### Official description

An input validation vulnerability exists in the Monitor Pro interface of MicroSCADA
Pro and MicroSCADA X SYS600. An authenticated user can launch an administrator level remote code execution irrespective of the authenticated user's role.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Hitachienergy Microscada Pro Sys600, Hitachienergy Microscada X Sys600.

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

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

## Is CVE-2022-3388 being exploited?

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

## Other vulnerabilities in Hitachi Energy MicroSCADA Pro SYS600

- [CVE-2024-3980](https://insights.sbomify.com/CVE-2024-3980/): Path traversal in MicroSCADA Pro SYS600 (critical 9.9)
- [CVE-2024-4872](https://insights.sbomify.com/CVE-2024-4872/): Code injection in MicroSCADA Pro SYS600 (critical 9.9)
- [CVE-2019-5620](https://insights.sbomify.com/CVE-2019-5620/): ABB MicroSCADA Pro SYS600 Missing Authentication for Critical Function (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3388 is a high-severity vulnerability in Hitachi Energy MicroSCADA Pro SYS600, published on 21 Nov 2022. 
Exploitation: There is no known exploitation of CVE-2022-3388 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-3388/ (Markdown: https://insights.sbomify.com/CVE-2022-3388/index.md)
```

## Sources

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

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