dbcve.org
OptodatalinkApplication · Opto22

CVE-2015-1006

CRITICAL · 9.8 CVSS v3.0 Published 2019-05-10
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
A vulnerable file in Opto 22 PAC Project Professional versions prior to R9.4006, PAC Project Basic versions prior to R9.4006, PAC Display Basic versions prior to R9.4f, PAC Display Professional versions prior to R9.4f, OptoOPCServer versions prior to R9.4c, and OptoDataLink version R9.4d and prior versions that were installed by PAC Project installer, versions prior to R9.4006, is susceptible to a heap-based buffer overflow condition that may allow remote code execution on the target system. Opto 22 suggests upgrading to the new product version as soon as possible.

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

A heap-based buffer overflow vulnerability exists in multiple Opto 22 PAC Project software components (PAC Project Professional/Basic, PAC Display Basic/Professional, OptoOPCServer, and OptoDataLink) in versions prior to R9.4006/R9.4f/R9.4c. The overflow occurs in a vulnerable file and can be exploited remotely to achieve arbitrary code execution on the target system.

MitigationUpgrade to the patched versions: R9.4006 or later for PAC Project, R9.4f or later for PAC Display, R9.4c or later for OptoOPCServer, and R9.4e or later for OptoDataLink.

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
OptodatalinkApplication
Affected:< r9.4d
OptoopcserverApplication
Affected:< r9.4c
Pac DisplayApplication
Affected:< r9.4f
Pac ProjectApplication
Affected:< r9.4006

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. List installed Opto 22 software
    Open Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName' to enumerate installed programs. Look for: PAC Project Professional, PAC Project Basic, PAC Display Professional, PAC Display Basic, OptoOPCServer, or OptoDataLink.
    Affected if Any of these Opto 22 products appear in the installed programs list
  2. Determine installed version of PAC Project
    If PAC Project Professional or Basic is installed, locate the main executable (typically in C:\Program Files\Opto22\PAC Project\ or C:\Program Files (x86)\Opto22\PAC Project\). Right-click the executable, select Properties, and check the Version tab for the product version.
    Affected if The version number is less than 9.4006 (for example, 9.4, 9.3, or earlier)
  3. Determine installed version of PAC Display
    If PAC Display Professional or Basic is installed, find the main executable (typically in C:\Program Files\Opto22\PAC Display\). Right-click and check the Version tab for the product version.
    Affected if The version number is less than 9.4f (for example, 9.4, 9.3e, or earlier)
  4. Determine installed version of OptoOPCServer
    If OptoOPCServer is installed, locate the executable (typically in C:\Program Files\Opto22\OptoOPCServer\). Right-click and check the Version tab for the product version.
    Affected if The version number is less than 9.4c (for example, 9.4b, 9.4a, or earlier)
  5. Determine installed version of OptoDataLink
    If OptoDataLink is installed, locate the executable (typically in C:\Program Files\Opto22\OptoDataLink\). Right-click and check the Version tab for the product version.
    Affected if The version number is less than 9.4d (for example, 9.4c, 9.4b, or earlier)

You are affected if any Opto 22 PAC Project software is installed with a version lower than the thresholds: PAC Project < 9.4006, PAC Display < 9.4f, OptoOPCServer < 9.4c, or OptoDataLink < 9.4d.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to the patched versions: R9.4006 or later for PAC Project, R9.4f or later for PAC Display, R9.4c or later for OptoOPCServer, and R9.4e or later for OptoDataLink.

Recommended fix Moderate confidence

PAC Project R9.4006 / PAC Display R9.4f / OptoOPCServer R9.4c / OptoDataLink R9.4e (or latest available)

  1. 1. Identify the installed Opto 22 product(s): PAC Project (Basic or Professional), PAC Display (Basic or Professional), OptoOPCServer, or OptoDataLink
  2. 2. Note the current installed version from the application's About or Help menu
  3. 3. Download the fixed version from Opto 22's official website or contact Opto 22 technical support
  4. 4. Back up any existing project files, configurations, and historical data
  5. 5. Install the new version: PAC Project R9.4006 or later, PAC Display R9.4f or later, OptoOPCServer R9.4c or later, OptoDataLink R9.4e or later (if available)
  6. 6. Re-deploy projects to PAC controllers if necessary
  7. 7. Verify the application launches without errors and all functionality works as expected
Caveat Review release notes for any configuration or feature changes between versions; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Optodatalink Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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