# CVE-2024-0715: EL Injection Vulnerability in Hitachi Global Link Manager

> An attacker can execute arbitrary code via Expression Language Injection in Hitachi Global Link Manager on Windows.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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:** No
- **Published:** 20 Feb 2024
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-2vp2-4cqw-xhcc

## What is CVE-2024-0715?

CVE-2024-0715 is a high-severity code injection vulnerability in Hitachi Global Link Manager, published on 20 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Expression Language Injection vulnerability in Hitachi Global Link Manager on Windows allows Code Injection.This issue affects Hitachi Global Link Manager: before 8.8.7-03.

Weakness: CWE-917 (Improper Neutralization of Special Elements used in an Expression Language Statement)

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

It affects 1 product.


Products: Hitachi Global Link Manager.

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

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

## Is CVE-2024-0715 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0715 is a high-severity code injection vulnerability in Hitachi Global Link Manager, published on 20 Feb 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-0715 in the wild and no public exploit code.

Affected product: Hitachi Global Link Manager. 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-0715/ (Markdown: https://insights.sbomify.com/CVE-2024-0715/index.md)
```

## Sources

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

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