CVE-2018-10592
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 FCJ controllers R4.02 and prior, FCN-100 controllers R4.02 and prior, FCN-RTU controllers R4.02 and prior, and FCN-500 controllers R4.02 and prior utilize hard-coded credentials that could allow an attacker to gain unauthorized administrative access to the device, which could result in remote code execution.
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 confidenceHard-coded credentials in Yokogawa STARDOM controllers (FCJ, FCN-100, FCN-RTU, FCN-500 all R4.02 and prior) allow unauthorized administrative access to the devices, which can be exploited to achieve remote code execution.
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.02<= r4.02<= r4.02<= r4.02CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelInventory all Yokogawa STARDOM controllers on the network (FCJ, FCN-100, FCN-RTU, FCN-500) by checking the device identification or management interfaceAffected if The device is any of these four models and has not been inventoried before
-
Check the installed firmware versionAccess the device management interface or use SNMP/sysinfo queries to retrieve the firmware versionAffected if The firmware version is R4.02 or prior for any of the affected models
-
Verify management interface accessibilityReview network firewall rules and access control lists to determine if the device web interface or administrative ports (typically HTTP/HTTPS, SSH, or Telnet) are exposed to untrusted networksAffected if The administrative interface is reachable from networks outside the trusted control system zone
-
Test for hard-coded credential exposureIf the hard-coded credentials for this CVE are known in your environment, attempt authentication to the device management interface using those credentials; otherwise, check device logs for successful unauthorized administrative loginsAffected if Authentication succeeds with credentials not issued by your organization or unauthorized admin sessions are logged
-
Review device account configurationExamine the local user accounts configured on the device through the management interface or configuration backupAffected if Unexpected administrative accounts exist that were not created by your security team
A user is affected if they operate any FCJ, FCN-100, FCN-RTU, or FCN-500 controller with firmware R4.02 or earlier that has its management interface accessible from any network where unauthorized actors could attempt login with the hard-coded credentials.
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 dataUpdate affected controllers to firmware newer than R4.02; if immediate updates are not possible, implement strict network segmentation, restrict external access to management interfaces, and monitor for attempts using the hardcoded credentials.
- Consultation12.0 h
- Implementation20.0 h
- Testing16.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 $15,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10592 — 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-10592 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