# CVE-2022-30707: Information disclosure in CAMS for HIS

> An adjacent attacker can compromise a machine to steal credentials, leading to data disclosure, alteration, or service disruption in Yokogawa CAMS for HIS systems.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-7gxw-4vp5-4rw9

## What is CVE-2022-30707?

CVE-2022-30707 is a high-severity vulnerability in Yokogawa Electric Corporation CAMS for HIS, published on 28 Jun 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Violation of secure design principles exists in the communication of CAMS for HIS. Affected products and versions are CENTUM series where LHS4800 is installed (CENTUM CS 3000 and CENTUM CS 3000 Small R3.08.10 to R3.09.00), CENTUM series where CAMS function is used (CENTUM VP, CENTUM VP Small, and CENTUM VP Basic R4.01.00 to R4.03.00), CENTUM series regardless of the use of CAMS function (CENTUM VP, CENTUM VP Small, and CENTUM VP Basic R5.01.00 to R5.04.20 and R6.01.00 to R6.09.00), Exaopc R3.72.00 to R3.80.00 (only if NTPF100-S6 'For CENTUM VP Support CAMS for HIS' is installed), B/M9000 CS R5.04.01 to R5.05.01, and B/M9000 VP R6.01.01 to R8.03.01). If an adjacent attacker successfully compromises a computer using CAMS for HIS software, they can use credentials from the compromised machine to access data from another machine using CAMS for HIS software. This can lead to a disabling of CAMS for HIS software functions on any affected machines, or information disclosure/alteration.

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

It affects 7 products.


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

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

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

## Is CVE-2022-30707 being exploited?

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

## Other vulnerabilities in Yokogawa Electric Corporation CAMS for HIS

- [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-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-2023-26593](https://insights.sbomify.com/CVE-2023-26593/): Hardcoded credentials in CENTUM series (high 7.8)
- [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-2022-30707 and fix it if it is affected.

What it is: CVE-2022-30707 is a high-severity vulnerability in Yokogawa Electric Corporation CAMS for HIS, published on 28 Jun 2022. 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-2022-30707 in the wild and no public exploit code.

Affected product: Yokogawa Electric Corporation CAMS for HIS. 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-30707/ (Markdown: https://insights.sbomify.com/CVE-2022-30707/index.md)
```

## Sources

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

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