Cyber Resilience

CVE-2024-0740

RCE in Eclipse Target Management ≤ 4.5.400

Published
26 April 2024
Modified
03 February 2025
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.012 67th percentile
Risk Priority 81 floored blend · peak EPSS

Summary

CVE-2024-0740 is a critical-severity OS Command Injection (CWE-78) vulnerability in Eclipse Target Management. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 33% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

Eclipse Target Management: Terminal and Remote System Explorer (RSE) versions up to and including 4.5.400 contain a remote code execution vulnerability tracked as CVE-2024-0740. The flaw is associated with CWE-78 and CWE-77, indicating improper neutralization of special elements used in OS commands, and carries a CVSS 3.1 score of 9.8 reflecting network attack vector, low complexity, and no required authentication or user interaction.

An unauthenticated attacker with network access can supply crafted input that results in arbitrary command execution on the affected system, potentially leading to full confidentiality, integrity, and availability impact on the host running the vulnerable Terminal or RSE components.

The vulnerability is addressed in the fixed version shipped with Eclipse IDE 2024-03; relevant changes are documented in Eclipse Git commits and the Eclipse Foundation security advisory at gitlab.eclipse.org/security/vulnerability-reports/-/issues/171.

EPSS for the CVE reached a recorded peak of 0.1236 on 2025-12-11 before receding to the current value of 0.0902.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1059.003 Windows Command Shell Execution
Adversaries may abuse the Windows command shell for execution.
T1059.004 Unix Shell Execution
Adversaries may abuse Unix shell commands and scripts for execution.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
T1059.008 Network Device CLI Execution
Adversaries may abuse scripting or built-in command line interpreters (CLI) on network devices to execute malicious command and payloads.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-10774Shared CWE-77, CWE-78
CVE-2026-2188Shared CWE-77, CWE-78
CVE-2026-12814Shared CWE-77, CWE-78
CVE-2025-15254Shared CWE-77, CWE-78
CVE-2026-1544Shared CWE-77, CWE-78
CVE-2026-8112Shared CWE-77, CWE-78
CVE-2026-15547Shared CWE-77, CWE-78
CVE-2026-5995Shared CWE-77, CWE-78
CVE-2026-6028Shared CWE-77, CWE-78
CVE-2026-10872Shared CWE-77, CWE-78

Affected Assets

eclipse
target management
≤ 4.5.400

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.2.3
  • V1.2.5
  • V1.2.8
  • V1.2.9

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover missing or incorrect command sanitization during development.

Input validation directly neutralizes or rejects special characters that would otherwise alter OS command structure.

Least privilege reduces the permissions available to any process that could be subverted by injected commands.

Least functionality restricts available OS commands and interpreters, limiting the blast radius of injection.

Secure engineering principles require proper neutralization of untrusted input before command construction.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

PR.PS-06's SDLC practices directly require secure coding and input handling that blocks command-injection defects, yet the single broad outcome leaves many specific neutralization vectors and verification gaps unaddressed.

DE.CM-09 partial match
prevents

Runtime monitoring of software and data can detect anomalous command execution resulting from injection.

ID.RA-01 partial match
prevents

Identifying recorded vulnerabilities enables remediation of command-injection flaws before exploitation.

PR.PS-02 partial match
prevents

Routine patching/maintenance can remediate known command-injection CVEs in dependencies (partial forward) but does nothing to stop developers from introducing improper neutralization in custom code (none reverse).

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

finds

Security testing and code review target insecure use of operating-system command interfaces, catching command-injection flaws introduced during development.

prevents

Secure development life cycle mandates input validation and command construction practices that directly prevent command injection.

prevents

Application security requirements explicitly call for controls against injection flaws including command injection.

prevents

Secure architecture principles reduce the attack surface but do not prescribe the specific neutralization techniques needed.

none

Environment separation limits the blast radius of an exploited command injection but does not prevent the flaw itself.

References