Skip to content
Fencer Intel
medium 5.3

CVE-2018-17902 json

Yokogawa STARDOM Controllers FCJ, FCN-100, FCN-RTU, FCN-500, All versions R4.10 and prior, The application utilizes multiple methods of ses…

published 8y ago modified 4mo ago also EUVD-2018-9643

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

Summary

Yokogawa STARDOM Controllers FCJ, FCN-100, FCN-RTU, FCN-500, All versions R4.10 and prior, The application utilizes multiple methods of session management which could result in a denial of service to the remote management functions.

Is CVE-2018-17902 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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 5.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.11% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Affected products

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

Classification

Weakness

References

Sources

Fencer Intel 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.