# CVE-2022-23130: Denial of service in GENESIS32

> Attackers can cause a denial of service in the database server by tricking users into importing malicious configuration files into Mitsubishi SCADA software.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:C/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Jan 2022
- **Updated:** 8 Jan 2026
- **Also known as:** GHSA-9q64-8g8h-wr27

## What is CVE-2022-23130?

CVE-2022-23130 is a medium-severity denial of service vulnerability in Mitsubishi Electric Corporation GENESIS32, published on 21 Jan 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Buffer Over-read vulnerability in Mitsubishi Electric MC Works64 versions 4.00A to 4.04E, Mitsubishi Electric GENESIS64 versions 10.97 and prior, Mitsubishi Electric Iconics Digital Solutions GENESIS64 versions 10.97 and prior, Mitsubishi Electric ICONICS Suite versions 10.97 and prior, Mitsubishi Electric Iconics Digital Solutions ICONICS Suite versions 10.97 and prior, Mitsubishi Electric GENESIS32 versions 9.7 and prior, and Mitsubishi Electric Iconics Digital Solutions GENESIS32 versions 9.7 and prior allows an attacker to cause a DoS condition in the database server by getting a legitimate user to import a configuration file containing specially crafted stored procedures into GENESIS64, ICONICS Suite, MC Works64, or GENESIS32 and execute commands against the database from GENESIS64, ICONICS Suite, MC Works64, or GENESIS32.

Weakness: CWE-125 (Out-of-bounds Read), CWE-126 (Buffer Over-read)

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

It affects 3 products.


Products: Iconics Genesis64, Iconics Hyper Historian, Mitsubishielectric Mc Works64.

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

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

## Is CVE-2022-23130 being exploited?

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

## Other vulnerabilities in Mitsubishi Electric Corporation GENESIS32

- [CVE-2022-33318](https://insights.sbomify.com/CVE-2022-33318/): Deserialization in GENESIS32 (critical 9.8)
- [CVE-2022-33319](https://insights.sbomify.com/CVE-2022-33319/): Information disclosure in GENESIS32 (high 8.2)
- [CVE-2024-7587](https://insights.sbomify.com/CVE-2024-7587/): Misconfiguration in GENESIS32 (high 7.8)
- [CVE-2022-33315](https://insights.sbomify.com/CVE-2022-33315/): Deserialization in GENESIS64 (high 7.8)
- [CVE-2022-33316](https://insights.sbomify.com/CVE-2022-33316/): Deserialization in GENESIS64 (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-23130 is a medium-severity denial of service vulnerability in Mitsubishi Electric Corporation GENESIS32, published on 21 Jan 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-23130 in the wild and no public exploit code.

Affected product: Mitsubishi Electric Corporation GENESIS32. 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-23130/ (Markdown: https://insights.sbomify.com/CVE-2022-23130/index.md)
```

## Sources

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

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