Loading vulnerability…
JetBrains PyCharm versions before 2020.3.4 insufficiently checked data when obtaining a project from version control systems (VCS). The insufficient validation could permit local code execution during the VCS project retrieval process.
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.
This repository is a proof-of-concept (PoC) for CVE-2021-30005, a vulnerability in JetBrains PyCharm (prior to version 2020.3.4) where opening a project containing a pre-made Python virtual environment could result in the automatic execution of arbitrary commands embedded in the environment's activation scripts. The exploit is implemented by placing a malicious command (e.g., launching gnome-calculator) in the 'venv/bin/activate' script. When a user clones the repository and opens it in a vulnerable PyCharm version, the IDE automatically activates the virtual environment, triggering the malicious command. The repository contains a full Python virtual environment with various activation scripts for different shells (bash, csh, fish, PowerShell), but the main exploit is in the bash activation script. The exploit demonstrates the risk of trusting project repositories with embedded virtual environments and highlights the importance of the 'Trusted Projects' feature introduced in PyCharm 2020.3.4. No network endpoints or remote command-and-control are present; the attack is purely local and relies on user interaction with the IDE.
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.