A code injection vulnerability exists in VMware Cloud Director versions 10.0.x before 10.0.0.2, 9.7.0.x before 9.7.0.5, 9.5.0.x before 9.5.0.6, and 9.1.0.x before 9.1.0.4. The vulnerability arises from improper input handling, allowing an authenticated attacker to inject and execute arbitrary code via the HTML5 and Flex-based UIs, the API Explorer, or API access.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a proof-of-concept exploit (exploit.py) for CVE-2020-3956, a remote code execution vulnerability in VMware vCloud Director. The exploit targets an expression injection flaw in the handling of the SMTP host field within the administrative API. By authenticating with valid credentials, the attacker can inject a crafted Java expression as the SMTP host, which is then evaluated by the server, leading to arbitrary command execution. The exploit is implemented in Python and requires the attacker to supply the target URL, username, and password. The README provides a brief description and references a technical advisory. The main code file, exploit.py, handles authentication, version detection, and payload delivery via the API. The exploit is operational and demonstrates real-world impact, but is not weaponized for mass exploitation. The main attack vector is network-based, targeting the vCloud Director administrative interface. Several fingerprintable endpoints are present, including the API paths used for authentication and email settings manipulation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.