CVE-2016-4860
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 FCN/FCJ controller R1.01 through R4.01 does not require authentication for Logic Designer connections, which allows remote attackers to reconfigure the device or cause a denial of service via a (1) stop application program, (2) change value, or (3) modify application command.
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 FCN/FCJ controllers (versions R1.01 through R4.01) have an authentication bypass vulnerability in the Logic Designer interface. Remote unauthenticated attackers can connect to the Logic Designer service without credentials and send commands to stop application programs, change values, or modify application logic, enabling device reconfiguration or denial of service.
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= r1.01= r2.01= r3.01= r4.01CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 modelDetermine if the target device is a Yokogawa STARDOM FCN or FCJ controller by checking the device identification, model number, or system documentationAffected if The device is a Yokogawa STARDOM FCN or FCJ controller
-
Check the firmware versionRetrieve the installed firmware version from the controller's system information, web interface, or management console, and compare against the affected versions: R1.01, R2.01, R3.01, R4.01Affected if The firmware version is R1.01, R2.01, R3.01, or R4.01
-
Verify Logic Designer service exposureCheck if the Logic Designer service port is listening and accessible on the network by scanning for open ports associated with the Logic Designer interface or reviewing network service listingsAffected if The Logic Designer service is exposed and reachable on the network
-
Confirm network accessibilityTest whether the Logic Designer interface can be reached from untrusted networks by attempting a connection from an external network segment or reviewing firewall rules and ACLsAffected if The Logic Designer interface is accessible from untrusted network segments without authentication barriers
A system is affected if it is a Yokogawa STARDOM FCN or FCJ controller running firmware version R1.01 through R4.01 with the Logic Designer interface exposed to network access.
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 dataIsolate affected controllers behind a firewall or ACLs to prevent unauthorized network access; contact Yokogawa for patched firmware and apply upgrades following ICS change management procedures.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-4860 — 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-2016-4860 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