# CVE-2018-16196: Denial of service in Multiple Yokogawa products that contain Vnet/IP Open Communication Driver

> Remote attackers can cause a denial of service in Yokogawa ICS products by stopping Vnet/IP Open Communication Driver communication.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r9jm-c64m-grf2

## What is CVE-2018-16196?

CVE-2018-16196 is a high-severity denial of service vulnerability in Multiple Yokogawa products that contain Vnet/IP Open Communication Driver, published on 9 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple Yokogawa products that contain Vnet/IP Open Communication Driver (CENTUM CS 3000(R3.05.00 - R3.09.50), CENTUM CS 3000 Entry Class(R3.05.00 - R3.09.50), CENTUM VP(R4.01.00 - R6.03.10), CENTUM VP Entry Class(R4.01.00 - R6.03.10), Exaopc(R3.10.00 - R3.75.00), PRM(R2.06.00 - R3.31.00), ProSafe-RS(R1.02.00 - R4.02.00), FAST/TOOLS(R9.02.00 - R10.02.00), B/M9000 VP(R6.03.01 - R8.01.90)) allows remote attackers to cause a denial of service attack that may result in stopping Vnet/IP Open Communication Driver's communication via unspecified vectors.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-16196?

It affects 9 products.


Products: Yokogawa B\/M9000 Vp, Yokogawa Centum Cs 3000 Entry Class, Yokogawa Centum Cs 3000 Firmware, Yokogawa Centum Vp Entry Class, Yokogawa Centum Vp Firmware, Yokogawa Exaopc, Yokogawa Fast\/Tools, Yokogawa Plant Resource Manager, Yokogawa Prosafe-Rs.

## How do I fix CVE-2018-16196?

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

## Is CVE-2018-16196 being exploited?

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

## Other vulnerabilities in Multiple Yokogawa products that contain Vnet/IP Open Communication Driver

- [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-2023-26593](https://insights.sbomify.com/CVE-2023-26593/): Hardcoded credentials in CENTUM series (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-16196 and fix it if it is affected.

What it is: CVE-2018-16196 is a high-severity denial of service vulnerability in Multiple Yokogawa products that contain Vnet/IP Open Communication Driver, published on 9 Jan 2019. 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-2018-16196 in the wild and no public exploit code.

Affected product: Multiple Yokogawa products that contain Vnet/IP Open Communication Driver. 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-2018-16196/ (Markdown: https://insights.sbomify.com/CVE-2018-16196/index.md)
```

## Sources

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

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