Skip to content
Fencer Vulns
high 8.1

CVE-2018-17896 json

Yokogawa STARDOM Controllers FCJ, FCN-100, FCN-RTU, FCN-500, All versions R4.10 and prior, The affected controllers utilize hard-coded cred…

published 2018-10-12 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-9637

cvss
8.1
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits
0
none known

Summary

Yokogawa STARDOM Controllers FCJ, FCN-100, FCN-RTU, FCN-500, All versions R4.10 and prior, The affected controllers utilize hard-coded credentials which may allow an attacker gain unauthorized access to the maintenance functions and obtain or modify information. This attack can be executed only during maintenance work.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-18-151-03 updated cvss 8.3

Yokogawa STARDOM Controllers (Update A)

  • Yokogawa STARDOM Controller FCJ <=(R4.10), <=(R4.02) Yokogawa STARDOM Controller FCN-100 <=(R4.02), <=(R4.10) Yokogawa STARDOM Controller FCN-500 <=(R4.02), <=(R4.10) Yokogawa STARDOM Controller FCN-RTU <=(R4.10), <=(R4.02)
    affected: mitigation “Yokogawa recommends users with questions related to this report (or on obtaining the updates) please utilize the product inquiry contact details” yokogawa.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

1.21% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Affected products

  • Yokogawa STARDOM Controllers FCJ,FCN-100,FCN-RTU, FCN-500

Classification

Weakness
  • CWE-798 Use of Hard-coded Credentials

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.