# CVE-2022-31205: Information disclosure in n/a

> Attackers can read the Web UI password from memory via the FINS protocol without authentication, compromising access to Omron PLCs.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-c5rh-wr27-mrw6

## What is CVE-2022-31205?

CVE-2022-31205 is a high-severity vulnerability in n/a, published on 26 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Omron CS series, CJ series, and CP series PLCs through 2022-05-18, the password for access to the Web UI is stored in memory area D1449...D1452 and can be read out using the Omron FINS protocol without any further authentication.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 7 products.


Products: Omron Cp1w-Cif41 Firmware, Omron Sysmac Cj2h Firmware, Omron Sysmac Cj2m Firmware, Omron Sysmac Cp1e Firmware, Omron Sysmac Cp1h Firmware, Omron Sysmac Cp1l Firmware, Omron Sysmac Cs1 Firmware.

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

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

## Is CVE-2022-31205 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-31207](https://insights.sbomify.com/CVE-2022-31207/): Missing authorization in n/a (critical 9.8)
- [CVE-2022-31204](https://insights.sbomify.com/CVE-2022-31204/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-31205 is a high-severity vulnerability in n/a, published on 26 Jul 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-31205 in the wild and no public exploit code.

Affected product: n/a. 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-31205/ (Markdown: https://insights.sbomify.com/CVE-2022-31205/index.md)
```

## Sources

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

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