# CVE-2021-20599: Information disclosure in MELSEC iQ-R Series SIL2 Process CPU R08PSFCPU

> Remote attackers can intercept cleartext credentials to gain unauthorized access to Mitsubishi MELSEC iQ-R safety and process CPU modules.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 14 Oct 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-vf46-vqq9-hg36

## What is CVE-2021-20599?

CVE-2021-20599 is a critical vulnerability in Mitsubishi Electric Corporation MELSEC iQ-R Series SIL2 Process CPU R08PSFCPU, published on 14 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cleartext Transmission of Sensitive InformationCleartext transmission of sensitive information vulnerability in MELSEC iQ-R series Safety CPU R08/16/32/120SFCPU firmware versions "26" and prior and MELSEC iQ-R series SIL2 Process CPU R08/16/32/120PSFCPU firmware versions "11" and prior allows a remote unauthenticated attacker to login to a target CPU module by obtaining credentials other than password.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2021-20599?

It affects 8 products.


Products: Mitsubishielectric R08psfcpu Firmware, Mitsubishielectric R08sfcpu Firmware, Mitsubishielectric R120psfcpu Firmware, Mitsubishielectric R120sfcpu Firmware, Mitsubishielectric R16psfcpu Firmware, Mitsubishielectric R16sfcpu Firmware, Mitsubishielectric R32psfcpu Firmware, Mitsubishielectric R32sfcpu Firmware.

## How do I fix CVE-2021-20599?

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

## Is CVE-2021-20599 being exploited?

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

## Other vulnerabilities in Mitsubishi Electric Corporation MELSEC iQ-R Series SIL2 Process CPU R08PSFCPU

- [CVE-2021-20597](https://insights.sbomify.com/CVE-2021-20597/): Information disclosure in Mitsubishi Electric MELSEC iQ-R series Safety CPU modules R08/16/32/120SFCPU; Mitsubishi Electric MELSEC iQ-R series SIL2 Process CPU modules R08/16/32/120PSFCPU (critical 9.1)
- [CVE-2021-20594](https://insights.sbomify.com/CVE-2021-20594/): Information disclosure in Mitsubishi Electric MELSEC iQ-R series Safety CPU modules R08/16/32/120SFCPU; Mitsubishi Electric MELSEC iQ-R series SIL2 Process CPU modules R08/16/32/120PSFCPU (high 7.5)
- [CVE-2023-6815](https://insights.sbomify.com/CVE-2023-6815/): Information disclosure in MELSEC iQ-R Series SIL2 Process CPU R08PSFCPU (medium 6.5)
- [CVE-2021-20598](https://insights.sbomify.com/CVE-2021-20598/): Denial of service in MELSEC iQ-R series CPU modules R08/16/32/120SFCPU; R08/16/32/120PSFCPU (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-20599 and fix it if it is affected.

What it is: CVE-2021-20599 is a critical vulnerability in Mitsubishi Electric Corporation MELSEC iQ-R Series SIL2 Process CPU R08PSFCPU, published on 14 Oct 2021. 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-2021-20599 in the wild and no public exploit code.

Affected product: Mitsubishi Electric Corporation MELSEC iQ-R Series SIL2 Process CPU R08PSFCPU. 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-2021-20599/ (Markdown: https://insights.sbomify.com/CVE-2021-20599/index.md)
```

## Sources

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

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