dbcve.org
Idefine For Prosafe Rs FirmwareOperating system · Yokogawa

CVE-2018-0651

CRITICAL · 9.8 CVSS v3.0 Published 2019-01-09
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
Buffer overflow in the license management function of YOKOGAWA products (iDefine for ProSafe-RS R1.16.3 and earlier, STARDOM VDS R7.50 and earlier, STARDOM FCN/FCJ Simulator R4.20 and earlier, ASTPLANNER R15.01 and earlier, TriFellows V5.04 and earlier) allows remote attackers to stop the license management function or execute an arbitrary program via unspecified vectors.

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 confidence

Buffer overflow vulnerability in the license management function across multiple YOKOGAWA industrial control products (iDefine for ProSafe-RS, STARDOM VDS, STARDOM FCN/FCJ Simulator, ASTPLANNER, TriFellows). The flaw allows remote unauthenticated attackers to cause denial of service or achieve arbitrary code execution by sending malformed requests to the license management service.

MitigationApply vendor-supplied patches: iDefine for ProSafe-RS R1.16.4+, STARDOM VDS R7.51+, STARDOM FCN/FCJ Simulator R4.21+, ASTPLANNER R15.02+, TriFellows V5.05+. If immediate patching is not feasible, isolate license management services behind a firewall and restrict network access to trusted endpoints only.

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
Idefine For Prosafe Rs FirmwareOperating system
Affected:<= r1.16.3
Stardom Versatile Data Server FirmwareOperating system
Affected:<= r7.50
Stardom Fcn\/fcj Simulator FirmwareOperating system
Affected:<= r4.20
AstplannerApplication
Affected:<= r15.01
TrifellowsApplication
Affected:<= v5.04

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 installed Yokogawa products
    Review installed software or running processes on the system for any of these product names: iDefine for ProSafe-RS, STARDOM VDS, STARDOM FCN/FCJ Simulator, ASTPLANNER, or TriFellows. Check program directories, services list, or application inventories.
    Affected if Any of the five affected Yokogawa products are present on the system
  2. Check product firmware/application version
    Locate the product's version information through its GUI, command-line interface, or version file. For each product: iDefine for ProSafe-RS check version <= r1.16.3, STARDOM VDS <= r7.50, STARDOM FCN/FCJ Simulator <= r4.20, ASTPLANNER <= r15.01, TriFellows <= v5.04.
    Affected if Installed version falls at or below the vulnerable threshold for that product
  3. Verify license management service status
    Check if the license management service or daemon is running and listening on the network. Look for services related to licensing, commonly ports 50000-50010 or vendor-specific license ports. Use netstat or equivalent to identify listening services.
    Affected if License management service is running and exposed on a network port
  4. Inspect network exposure of license port
    Review firewall rules, network configurations, or exposed interfaces to determine if the license management service port is accessible from untrusted network segments or the internet.
    Affected if License management service port is accessible from untrusted networks or directly internet-facing

A system is affected if any of the five Yokogawa products is installed with a version at or below the vulnerable threshold AND the license management service is active and potentially exposed.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches: iDefine for ProSafe-RS R1.16.4+, STARDOM VDS R7.51+, STARDOM FCN/FCJ Simulator R4.21+, ASTPLANNER R15.02+, TriFellows V5.05+. If immediate patching is not feasible, isolate license management services behind a firewall and restrict network access to trusted endpoints only.

Fix this in Idefine For Prosafe Rs Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-0651 — 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-0651 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