# CVE-2023-26593: Hardcoded credentials in CENTUM series

> Attackers with local access can escalate privileges by tampering with cleartext password files in Yokogawa CENTUM systems using specific authentication modes.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2023
- **Updated:** 10 Feb 2025
- **Also known as:** GHSA-hfx7-v8g3-wm7q

## What is CVE-2023-26593?

CVE-2023-26593 is a high-severity vulnerability in Yokogawa Electric Corporation CENTUM series, published on 11 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

CENTUM series provided by Yokogawa Electric Corporation are vulnerable to cleartext storage of sensitive information. If an attacker who can login or access the computer where the affected product is installed tampers the password file stored in the computer, the user privilege which CENTUM managed may be escalated. As a result, the control system may be operated with the escalated user privilege. To exploit this vulnerability, the following prerequisites must be met: (1)An attacker has obtained user credentials where the affected product is installed, (2)CENTUM Authentication Mode is used for user authentication when CENTUM VP is used. The affected products and versions are as follows: CENTUM CS 1000, CENTUM CS 3000 (Including CENTUM CS 3000 Entry Class) R2.01.00 to R3.09.50, CENTUM VP (Including CENTUM VP Entry Class) R4.01.00 to R4.03.00, R5.01.00 to R5.04.20, and R6.01.00 and later, B/M9000 CS R5.04.01 to R5.05.01, and B/M9000 VP R6.01.01 to R7.04.51 and R8.01.01 and later

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

## Which versions are affected by CVE-2023-26593?

It affects 8 products.


Products: Yokogawa B\/M9000 Vp, Yokogawa B\/M9000cs, Yokogawa Centum Cs 1000, Yokogawa Centum Cs 3000, Yokogawa Centum Cs 3000 Entry Class, Yokogawa Centum Vp, Yokogawa Centum Vp Entry Class, Yokogawa Exaopc.

## How do I fix CVE-2023-26593?

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

## Is CVE-2023-26593 being exploited?

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

## Other vulnerabilities in Yokogawa Electric Corporation CENTUM series

- [CVE-2022-26034](https://insights.sbomify.com/CVE-2022-26034/): Auth bypass in CENTUM VP series with VP6E5000(AD Suite Engineering ServerFunction) installed and B/M9000 VP (critical 9.1)
- [CVE-2022-30707](https://insights.sbomify.com/CVE-2022-30707/): Information disclosure in CAMS for HIS (high 8.8)
- [CVE-2014-3888](https://insights.sbomify.com/CVE-2014-3888/): Memory corruption in n/a (high 8.3)
- [CVE-2014-0782](https://insights.sbomify.com/CVE-2014-0782/): Yokogawa CENTUM CS 3000 Stack-based Buffer Overflow (high 8.3)
- [CVE-2022-27188](https://insights.sbomify.com/CVE-2022-27188/): Command injection in CENTUM VP series with VP6E5150(Graphic Builder) installed and B/M9000 VP (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-26593 and fix it if it is affected.

What it is: CVE-2023-26593 is a high-severity vulnerability in Yokogawa Electric Corporation CENTUM series, published on 11 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-26593 in the wild and no public exploit code.

Affected product: Yokogawa Electric Corporation CENTUM series. 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-2023-26593/ (Markdown: https://insights.sbomify.com/CVE-2023-26593/index.md)
```

## Sources

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

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