Skip to main content
Mallory
CriticalCISA KEVExploited in the wildPublic exploit

Unauthenticated command injection in Cleo Harmony, VLTrader, and LexiCom Autorun handling

IdentifiersCVE-2024-55956CWE-78

CVE-2024-55956 affects Cleo Harmony, VLTrader, and LexiCom before version 5.8.0.24. According to the provided content, an unauthenticated attacker can leverage the default settings of the Autorun directory to import and execute arbitrary Bash or PowerShell commands on the underlying host system. Supporting reporting also characterizes the issue as enabling unauthorized import or execution of arbitrary commands and places it in the context of exploitation against Cleo managed file transfer deployments. The vulnerability was fixed in version 5.8.0.24.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote unauthenticated execution of attacker-controlled operating system commands on the host running the vulnerable Cleo product. In observed intrusions, attackers used this access to deploy Java-based backdoors such as Malichus, conduct data theft, maintain persistence, and perform further post-exploitation activity. The practical impact therefore includes full compromise of the affected MFT server, theft of files and sensitive business data handled by the platform, and use of the server as a foothold for additional intrusion activity.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, reduce exposure of vulnerable Cleo instances as much as operationally feasible, especially any internet-accessible deployment. Restrict access to the affected service/endpoints to trusted networks, disable or tightly control use of Autorun-related functionality where possible, and monitor for unexpected file imports, command execution, shell activity, and creation of suspicious Java artifacts or backdoors. Given active exploitation, mitigation should be treated only as temporary risk reduction until upgrade to 5.8.0.24 or later is completed.

Remediation

Patch, then assume compromise.

Upgrade Cleo Harmony, VLTrader, and LexiCom to version 5.8.0.24 or later, as the provided content states this version fixes CVE-2024-55956. Because the vulnerability has been reported as exploited in the wild, remediation should also include incident-response validation on previously exposed systems: review for unauthorized files or imports, inspect for persistence mechanisms and Java backdoors such as Malichus, rotate credentials that may have been exposed to the MFT environment, and assess downstream systems for follow-on compromise.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
CleoHarmonyapplication
CleoLexicomapplication
CleoVltraderapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence5

Every observed campaign linking this CVE to a named adversary.

Associated malware5

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.