Loading vulnerability…
CVE-2024-3121 is a remote code execution vulnerability in the create_conda_env function of parisneo/lollms version 5.9.0. The function invokes subprocess.Popen with shell=True and incorporates the env_name and python_version parameters into the shell command. An attacker able to manipulate these parameters can inject and execute arbitrary operating-system commands in the context of the LoLLMS 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 demonstrates a proof-of-concept (POC) exploit for CVE-2024-3121, a remote code execution (RCE) vulnerability in the 'parisneo/lollms' framework. The vulnerability arises from unsanitized user input ('env_name') being directly interpolated into a shell command in the 'create_conda_env' function, allowing for shell command injection. The repository contains two files: a README.md that documents the vulnerability, its impact, and references, and an 'exploit.py' script that demonstrates exploitation by injecting the 'whoami' command via the 'env_name' parameter. The exploit targets both Linux and Windows platforms, adjusting the path to the 'conda' executable accordingly. The main attack vector is remote, as the vulnerable function could be exposed via a network API in the target application. The exploit's payload is a simple command injection, and the code serves as a clear demonstration of the vulnerability rather than a weaponized attack tool.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.