# CVE-2024-1531: File upload in RTU500 series CMU firmware

> An authorized user can upload a malicious file to leak random memory content into the RTU500 system log, exposing sensitive data.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2024
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vpmw-w5fr-gf3h

## What is CVE-2024-1531?

CVE-2024-1531 is a high-severity vulnerability in Hitachi Energy RTU500 series CMU firmware, published on 27 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability exists in the stb-language file handling that affects the RTU500 series product versions listed below. A malicious actor could print random memory content in the RTU500 system log, if an authorized user uploads a specially crafted stb-language file.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2024-1531 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1531 is a high-severity vulnerability in Hitachi Energy RTU500 series CMU firmware, published on 27 Mar 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-1531 in the wild and no public exploit code.

Affected product: Hitachi Energy RTU500 series CMU firmware. 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-1531/ (Markdown: https://insights.sbomify.com/CVE-2024-1531/index.md)
```

## Sources

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

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