dbcve.org
ExaopcApplication · Yokogawa

CVE-2019-6008

HIGH · 7.8 CVSS v3.1 Published 2019-12-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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
An unquoted search path vulnerability in Multiple Yokogawa products for Windows (Exaopc (R1.01.00 ? R3.77.00), Exaplog (R1.10.00 ? R3.40.00), Exaquantum (R1.10.00 ? R3.02.00 and R3.15.00), Exaquantum/Batch (R1.01.00 ? R2.50.40), Exasmoc (all revisions), Exarqe (all revisions), GA10 (R1.01.01 ? R3.05.01), and InsightSuiteAE (R1.01.00 ? R1.06.00)) allow local users to gain privileges via a Trojan horse executable file and execute arbitrary code with eleveted privileges.

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

Unquoted service path vulnerability in multiple Yokogawa Windows products allows local attackers to place malicious executables in intermediate directories along service paths containing spaces, which Windows will execute before the intended binary due to improper path quoting, resulting in arbitrary code execution with elevated (SYSTEM) privileges.

MitigationIdentify unquoted service executable paths in affected products and either add quotes around the path in the Windows service configuration or remove write permissions from intermediate directories in the path to prevent Trojan horse injection.

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
ExaopcApplication
Affected:>= r1.01.00, <= r3.77.00
ExaplogApplication
Affected:>= r1.10.00, <= r3.30.00
ExaquantumApplication
Affected:>= r1.10.00, <= r3.02.00
Exaquantum\/batchApplication
Affected:>= r1.01.00, <= r2.50.40
ExarqeApplication
Affected:all versions
ExasmocApplication
Affected:all versions
Ga10Application
Affected:>= r1.01.01, <= r3.05.01
InsightsuiteaeApplication
Affected:>= r1.01.00, <= r1.06.00

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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
    Open Windows Registry and check HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Yokogawa entries, or look in common installation folders such as C:\Program Files\Yokogawa or C:\Program Files (x86)\Yokogawa
    Affected if Any of the following products are installed: Exaopc, Exaplog, Exaquantum, Exaquantum/batch, Exarqe, Exasmoc, Ga10, or Insightsuiteae
  2. Find Windows services associated with Yokogawa products
    Open Command Prompt as Administrator and run 'sc query state= all' to list all services, then filter for Yokogawa-related service names using 'findstr /i yokogawa'
    Affected if Any Yokogawa-related Windows services exist on the system
  3. Check executable path configuration for each Yokogawa service
    For each identified Yokogawa service, run 'sc qc <service_name>' and examine the BINARY_PATH_NAME field
    Affected if The BINARY_PATH_NAME contains spaces and is not enclosed in quotation marks (e.g., path is C:\Program Files\Yokogawa\bin\service.exe instead of "C:\Program Files\Yokogawa\bin\service.exe")
  4. Verify write permissions on intermediate directories in unquoted paths
    For each unquoted path with spaces, use icacls to check write permissions on each directory in the path (e.g., run 'icacls "C:\Program Files\Yokogawa"' to check the intermediate directory)
    Affected if Users or groups other than Administrators and SYSTEM have write (WD) or write-execute (WE) permissions on any intermediate directory in the service path

You are affected if a Yokogawa product from the affected list is installed, has a corresponding Windows service, and that service has an unquoted executable path containing spaces with writable intermediate directories.

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

Identify unquoted service executable paths in affected products and either add quotes around the path in the Windows service configuration or remove write permissions from intermediate directories in the path to prevent Trojan horse injection.

Fix this in Exaopc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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