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

> Local attackers can extract sensitive passwords from Omron CX-One and PLC object files due to reversible storage formats.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Oct 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-38vh-mhxc-849f

## What is CVE-2015-1015?

CVE-2015-1015 is a low-severity vulnerability in n/a, published on 3 Oct 2015. It can only be exploited from the same machine or local network, 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 use a reversible format for password storage in object files on Compact Flash cards, which makes it easier for local users to obtain sensitive information by reading a file.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 3 products.


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

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

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

## Is CVE-2015-1015 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-0987](https://insights.sbomify.com/CVE-2015-0987/): Information disclosure in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-1015 is a low-severity vulnerability in n/a, published on 3 Oct 2015. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-1015 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-1015/ (Markdown: https://insights.sbomify.com/CVE-2015-1015/index.md)
```

## Sources

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

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