# CVE-2024-0740: Eclipse Target Management <= 4.5.500 Command Injection

> Remote attackers can execute arbitrary commands without authentication in Eclipse Target Management, requiring an upgrade to the latest IDE version.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Apr 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-wv9c-r7wv-3wph

## What is CVE-2024-0740?

CVE-2024-0740 is a critical command injection vulnerability in Eclipse Target Management, published on 26 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Eclipse Target Management: Terminal and Remote System Explorer (RSE) version <= 4.5.400 has a remote code execution vulnerability that does not require authentication. 

The fixed version is included in Eclipse IDE 2024-03

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Eclipse Target Management.

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

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

## Is CVE-2024-0740 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0740 is a critical command injection vulnerability in Eclipse Target Management, published on 26 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-0740 in the wild and no public exploit code.

Affected product: Eclipse Target Management. 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-0740/ (Markdown: https://insights.sbomify.com/CVE-2024-0740/index.md)
```

## Sources

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

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