# CVE-2024-2097: Code injection in MACH SCM Server

> An authenticated attacker can execute arbitrary code remotely on Hitachi MACH SCM servers via malicious LINQ queries.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Mar 2024
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-x6rr-6p9v-45m4

## What is CVE-2024-2097?

CVE-2024-2097 is a high-severity code injection vulnerability in Hitachi Energy MACH SCM Server, published on 27 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An authenticated malicious client can send a special LINQ query
to execute arbitrary code remotely (RCE) on the SCM server
from List control, and execute the arbitrary code on the same
system where SCMArchivedEventViewerTool is installed in the
case of SCM Tools.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

Apply the vendor's patch.

## Is CVE-2024-2097 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-2097 is a high-severity code injection vulnerability in Hitachi Energy MACH SCM Server, published on 27 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-2097 in the wild and no public exploit code.

Affected product: Hitachi Energy MACH SCM Server. 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-2097/ (Markdown: https://insights.sbomify.com/CVE-2024-2097/index.md)
```

## Sources

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

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