dbcve.org
Fcj FirmwareOperating system · Yokogawa

CVE-2018-17900

CRITICAL · 9.8 CVSS v3.0 Published 2018-10-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Yokogawa STARDOM Controllers FCJ, FCN-100, FCN-RTU, FCN-500, All versions R4.10 and prior, The web application improperly protects credentials which could allow an attacker to obtain credentials for remote access to controllers.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Yokogawa STARDOM Controllers (FCJ, FCN-100, FCN-RTU, FCN-500) web application improperly protects credentials, allowing attackers to obtain credentials for remote access to the ICS controllers. This is a critical vulnerability (CVSS 9.8) affecting all versions R4.10 and prior, enabling unauthenticated credential theft from the web interface.

MitigationUpgrade firmware to a version beyond R4.10 that properly protects credentials, and immediately change all exposed credentials. Implement network segmentation and monitor for unauthorized access attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Fcj FirmwareOperating system
Affected:<= r4.10
Fcn 100 FirmwareOperating system
Affected:<= r4.10
Fcn Rtu FirmwareOperating system
Affected:<= r4.10
Fcn 500 FirmwareOperating system
Affected:<= r4.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Yokogawa STARDOM controller model
    Access the controller's web interface or system information to confirm the model is one of: FCJ, FCN-100, FCN-RTU, or FCN-500
    Affected if The model is any of FCJ, FCN-100, FCN-RTU, or FCN-500 and the web interface is accessible
  2. Check the firmware version
    Access the controller's web interface or system settings to determine the firmware revision. Typical locations include the system info page, firmware update section, or about page in the web application
    Affected if The firmware version is R4.10 or any version prior to R4.10
  3. Verify if the web interface is accessible over the network
    Attempt to reach the web interface via HTTP/HTTPS from a network location. Check if port 80, 443, or the configured web service port responds
    Affected if The web interface is reachable from network segments that are not strictly controlled
  4. Test for unauthenticated credential access
    Inspect the web application responses without logging in. Look for credential-related endpoints, API calls, or configuration pages that may return authentication data without requiring authentication
    Affected if The web application returns credential data, session tokens, or authentication parameters without requiring valid authentication credentials

You are affected if you have a Yokogawa STARDOM controller (FCJ, FCN-100, FCN-RTU, or FCN-500) running firmware R4.10 or earlier with an accessible web interface that exposes credentials without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade firmware to a version beyond R4.10 that properly protects credentials, and immediately change all exposed credentials. Implement network segmentation and monitor for unauthorized access attempts.

Recommended fix Moderate confidence

Firmware version greater than R4.10 (specific fixed release available from Yokogawa)

  1. 1. Identify all affected Yokogawa STARDOM Controllers (FCJ, FCN-100, FCN-RTU, FCN-500) in the environment.
  2. 2. Document current firmware versions of each controller to confirm they are running R4.10 or prior.
  3. 3. Review Yokogawa's official firmware release notes and security advisories on their support portal to identify the fixed release version.
  4. 4. Obtain the fixed firmware version from Yokogawa's official sources (referenced at web-material3.yokogawa.com).
  5. 5. Follow Yokogawa's standard firmware update procedure for STARDOM controllers, ensuring proper backup of configuration data before upgrading.
  6. 6. After upgrading, verify the web application's credential handling has been corrected.
  7. 7. Change all credentials that may have been exposed, as a precautionary measure.
Caveat Firmware upgrades may require controller downtime and could impact dependent processes - plan maintenance window accordingly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fcj Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
36.0 hours of engineering $6,340
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-17900 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-17900 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data