# CVE-2022-21177: Path traversal in CENTUM CS 3000

> A path traversal vulnerability in Yokogawa CENTUM and Exaopc Log Server allows attackers to read or modify arbitrary files.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-v687-84r6-73vp

## What is CVE-2022-21177?

CVE-2022-21177 is a high-severity path traversal vulnerability in Yokogawa Electric Corporation CENTUM CS 3000, published on 11 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

There is a path traversal vulnerability in CAMS for HIS Log Server contained in the following Yokogawa Electric products: CENTUM CS 3000 versions from R3.08.10 to R3.09.00, CENTUM VP versions from R4.01.00 to R4.03.00, from R5.01.00 to R5.04.20, andfrom R6.01.00 to R6.08.00, Exaopc versions from R3.72.00 to R3.79.00.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-23 (Relative Path Traversal)

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

It affects 5 products.


Products: Yokogawa Centum Cs 3000 Entry Firmware, Yokogawa Centum Cs 3000 Firmware, Yokogawa Centum Vp Entry Firmware, Yokogawa Centum Vp Firmware, Yokogawa Exaopc.

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

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

## Is CVE-2022-21177 being exploited?

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

## Other vulnerabilities in Yokogawa Electric Corporation CENTUM CS 3000

- [CVE-2022-21808](https://insights.sbomify.com/CVE-2022-21808/): Path traversal in CENTUM CS 3000 (high 8.8)
- [CVE-2022-22729](https://insights.sbomify.com/CVE-2022-22729/): Auth bypass in CENTUM CS 3000 (high 8.8)
- [CVE-2022-22145](https://insights.sbomify.com/CVE-2022-22145/): Denial of service in CENTUM CS 3000 (high 8.1)
- [CVE-2022-22151](https://insights.sbomify.com/CVE-2022-22151/): Other in CENTUM CS 3000 (high 8.1)
- [CVE-2022-22141](https://insights.sbomify.com/CVE-2022-22141/): Privilege escalation in CENTUM CS 3000 (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-21177 is a high-severity path traversal vulnerability in Yokogawa Electric Corporation CENTUM CS 3000, published on 11 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-21177 in the wild and no public exploit code.

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

## Sources

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

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