CVE-2018-17896
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 · uneditedYokogawa 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.
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 · high confidenceYokogawa STARDOM controllers (FCJ, FCN-100, FCN-RTU, FCN-500) have hard-coded credentials embedded in firmware that provide unauthorized access to maintenance functions, allowing attackers to obtain or modify controller information.
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<= r4.10<= r4.10<= r4.10<= r4.10CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify STARDOM controller modelAccess the controller management interface or check device documentation to determine if the model is FCJ, FCN-100, FCN-RTU, or FCN-500Affected if Model is any of FCJ, FCN-100, FCN-RTU, or FCN-500
-
Check firmware versionLog into the controller via its management interface or use the vendor-supplied utility to retrieve the firmware version. Compare the installed version against r4.10Affected if Firmware version is r4.10 or earlier
-
Verify hard-coded credential presenceExamine firmware files or configuration dumps for embedded credential strings. Yokogawa advisories typically document these as maintenance-level accounts with fixed passwordsAffected if Firmware contains hard-coded accounts with static passwords
-
Test default credential accessibilityAttempt authentication using the documented hard-coded credentials against the maintenance interface or service ports (such as port 80/443 web interfaces or terminal services)Affected if Default hard-coded credentials successfully authenticate
-
Review access logs for unauthorized maintenance accessInspect controller audit logs or network traffic logs for successful authentications originating from unexpected IP addresses or at unusual times using maintenance functionsAffected if Unrecognized authentications to maintenance functions are logged
If the controller is an FCJ, FCN-100, FCN-RTU, or FCN-500 model running firmware r4.10 or earlier, the environment contains the hard-coded credential vulnerability.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataReplace hard-coded credentials with unique, strong passwords or implement proper credential management. Coordinate with Yokogawa for vendor-specific remediation procedures and ensure credential changes occur during planned maintenance windows.
- Consultation12.0 h
- Implementation20.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-17896 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-17896 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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