CVE-2024-55956
RCE in Cleo Harmony ≤ 5.8.0.24
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-55956 is a critical-severity Command Injection (CWE-77) vulnerability in Cleo Harmony. 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 0.2% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities 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.
Cleo Harmony, VLTrader, and LexiCom versions prior to 5.8.0.24 contain a command injection vulnerability tracked as CVE-2024-55956 and CWE-77. The flaw allows an unauthenticated remote user to import and execute arbitrary Bash or PowerShell commands on the underlying host by abusing the products' default Autorun directory configuration. The issue carries a CVSS 3.1 score of 9.8, reflecting network-accessible attack complexity that requires no credentials or user interaction.
An attacker can send specially crafted files or commands to the affected transfer-management software and obtain arbitrary code execution with the privileges of the service account. Successful exploitation grants full control over the host system, enabling data theft, persistence, lateral movement, or ransomware deployment.
Cleo has published security advisories and remediation guidance directing customers to upgrade to version 5.8.0.24 or later. The vulnerability appears in CISA's Known Exploited Vulnerabilities catalog, confirming that federal agencies must apply the vendor patch according to the published timeline.
Huntress has reported active exploitation of the flaw in the wild. The associated EPSS score reached a peak of 0.9675 and currently stands at 0.9122, indicating sustained attacker interest after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-52864
Vulnerability Data
In Cleo Harmony before 5.8.0.24, VLTrader before 5.8.0.24, and LexiCom before 5.8.0.24, an unauthenticated user can import and execute arbitrary Bash or PowerShell commands on the host system by leveraging the default settings of the Autorun directory.
- CWE(s)
- KEV Date Added
- 17 December 2024
Related Threats
Threat-Actor AttributionAI
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.3V1.2.5V1.2.8V1.2.9
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover command-construction flaws before deployment.
Input validation directly stops construction of commands from untrusted data containing special elements.
Secure engineering principles include proper neutralization and safe command construction practices.
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.
Secure SDLC practices directly require input validation and neutralization that prevent command injection.
Runtime monitoring of software and data can detect anomalous command execution resulting from injection.
Identifying recorded vulnerabilities enables remediation of command-injection flaws before exploitation.
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.
Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.
Security testing in development catches command-injection vulnerabilities before release.
Secure development life cycle mandates input validation and command construction practices that directly prevent command injection.
Application security requirements explicitly call for controls against injection flaws including command injection.
Secure architecture principles reduce the attack surface but do not prescribe the specific neutralization techniques needed.
Environment separation limits the blast radius of an exploited command injection but does not prevent the flaw itself.