# CVE-2015-0987: Information disclosure in n/a

> Remote attackers can sniff cleartext passwords during PLC unlock requests to obtain sensitive information, affecting Omron CX-One and CJ series PLCs.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Oct 2015
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-pjf3-6cr6-cfg3

## What is CVE-2015-0987?

CVE-2015-0987 is a critical vulnerability in n/a, published on 3 Oct 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2015-0987?

It affects 3 products.


Products: Omron Cj2h Plc, Omron Cj2m Plc, Omron Cx-Programmer.

## How do I fix CVE-2015-0987?

No fix has been published for CVE-2015-0987 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-0987 being exploited?

There is no known exploitation of CVE-2015-0987 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2015-1015](https://insights.sbomify.com/CVE-2015-1015/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-0987 and fix it if it is affected.

What it is: CVE-2015-0987 is a critical vulnerability in n/a, published on 3 Oct 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-0987 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-0987/ (Markdown: https://insights.sbomify.com/CVE-2015-0987/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-0987
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-0987
- OSV: https://osv.dev/vulnerability/CVE-2015-0987

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-0987/
Summaries are generated and may contain mistakes; the official description above is the record.