# CVE-2024-31412: Information disclosure in CX-Programmer

> An attacker can cause information disclosure or application crash by tricking a user into opening a specially crafted project file in OMRON CX-Programmer.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-r83m-mr5x-xj66

## What is CVE-2024-31412?

CVE-2024-31412 is a high-severity vulnerability in OMRON Corporation CX-Programmer, published on 1 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Out-of-bounds read vulnerability exists in CX-Programmer included in CX-One CXONE-AL[][]D-V4 Ver. 9.81 or lower. Opening a specially crafted project file may lead to information disclosure and/or the product being crashed.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2024-31412?


## How do I fix CVE-2024-31412?

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

## Is CVE-2024-31412 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-31412 and fix it if it is affected.

What it is: CVE-2024-31412 is a high-severity vulnerability in OMRON Corporation CX-Programmer, published on 1 May 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-31412 in the wild and no public exploit code.

Affected product: OMRON Corporation CX-Programmer. 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-2024-31412/ (Markdown: https://insights.sbomify.com/CVE-2024-31412/index.md)
```

## Sources

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

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