dbcve.org
Cx ProgrammerApplication · Omron

CVE-2015-0987

CRITICAL · 10.0 CVSS v3.1 Published 2015-10-06
Fix available
A fix is available. Upgrade to after 9.5 or later.
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
Omron CX-One CX-Programmer before 9.6, CJ2M PLC devices before 2.1, and CJ2H PLC devices before 1.5 rely on cleartext password transmission, which allows remote attackers to obtain sensitive information by sniffing the network during a PLC unlock request.

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

Omron CX-Programmer before version 9.6 and CJ2M/CJ2H PLC devices transmit passwords in cleartext during unlock requests, allowing remote attackers on the network to capture plaintext credentials via sniffing.

MitigationUpgrade to CX-Programmer 9.6+ and PLC firmware 2.1+ (CJ2M) / 1.5+ (CJ2H), and implement network segmentation or VPN to protect PLC communications from unauthorized sniffing.

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
Cx ProgrammerApplication
Affected:<= 9.5
Cj2h PlcHardware / appliance
Affected:<= 1.4
Cj2m PlcHardware / appliance
Affected:<= 2.0

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
Changed
Confidentiality
High
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/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. Check CX-Programmer version
    Open CX-Programmer and navigate to Help > About, or view the installed program version in Windows Add/Remove Programs
    Affected if Version is 9.5 or earlier (any version <= 9.5)
  2. Check CJ2H PLC firmware version
    Connect to the PLC using CX-Programmer and inspect the device information, or check the firmware version displayed in the PLC's online diagnostics
    Affected if Firmware version is 1.4 or earlier (any version <= 1.4)
  3. Check CJ2M PLC firmware version
    Connect to the PLC using CX-Programmer and inspect the device information, or check the firmware version displayed in the PLC's online diagnostics
    Affected if Firmware version is 2.0 or earlier (any version <= 2.0)
  4. Verify network traffic contains plaintext credentials
    Use a network capture tool on the segment where PLC communications occur to observe unlock request packets
    Affected if Capture reveals plaintext passwords in unlock request traffic

A user is affected if any installed CX-Programmer version is <= 9.5, any CJ2H PLC firmware is <= 1.4, any CJ2M PLC firmware is <= 2.0, or if plaintext passwords are observed in network traffic.

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
Upgrade available Upgrade to a release after 9.5
Interim mitigation

Upgrade to CX-Programmer 9.6+ and PLC firmware 2.1+ (CJ2M) / 1.5+ (CJ2H), and implement network segmentation or VPN to protect PLC communications from unauthorized sniffing.

Recommended fix High confidence

CX-Programmer 9.6, CJ2M PLC firmware 2.1, CJ2H PLC firmware 1.5

  1. Back up all current project files, PLC programs, and configurations before upgrading
  2. Download Omron CX-One suite version 9.6 or later from the official Omron website (or authorized distributor)
  3. Install CX-Programmer 9.6 or later as part of the CX-One suite upgrade
  4. For CJ2M PLC devices: Update firmware to version 2.1 or later using CX-Programmer's firmware update feature
  5. For CJ2H PLC devices: Update firmware to version 1.5 or later using CX-Programmer's firmware update feature
  6. After upgrading, verify the fix by attempting to capture network traffic during a PLC unlock request to confirm passwords are no longer transmitted in cleartext
  7. Test all PLC programs and communications to ensure proper operation after the upgrade
Caveat Standard upgrade risks apply - review release notes for any changes to programming features or communication protocols that may affect existing projects

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

Fix this in Cx Programmer Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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