# CVE-2024-3121: Remote Code Execution in create_conda_env function in parisneo/lollms

> Attackers can execute arbitrary commands via the create_conda_env function due to unsafe shell execution, affecting users of the lollms library.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-79h8-gxhq-q3jg, PYSEC-2026-1584

## What is CVE-2024-3121?

CVE-2024-3121 is a medium-severity command injection vulnerability in parisneo/lollms, published on 24 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A remote code execution vulnerability exists in the create_conda_env function of the parisneo/lollms repository, version 5.9.0. The vulnerability arises from the use of shell=True in the subprocess.Popen function, which allows an attacker to inject arbitrary commands by manipulating the env_name and python_version parameters. This issue could lead to a serious security breach as demonstrated by the ability to execute the 'whoami' command among potentially other harmful commands.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2024-3121?

3 open source packages ship an affected version, including lollms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lollms` | PyPI | All versions to 9.5.1 | None |
| `lollms` | PyPI | All versions to 9.5.1 | None |
| `lollms` | PyPI | All versions to 9.5.1 | None |

Products: Lollms Lollms.

## How do I fix CVE-2024-3121?

No fix has been published for CVE-2024-3121 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-3121 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3121 exists.

Public exploit code:

- Remote Code Execution in create_conda_env function in parisneo/lollms (github_poc): https://github.com/dark-ninja10/CVE-2024-3121

## Other vulnerabilities in parisneo/lollms

- [CVE-2026-1114](https://insights.sbomify.com/CVE-2026-1114/): Improper Access Control via Weak JWT Token in parisneo/lollms (critical 9.8)
- [CVE-2024-3429](https://insights.sbomify.com/CVE-2024-3429/): Path Traversal in parisneo/lollms (critical 9.8)
- [CVE-2026-1115](https://insights.sbomify.com/CVE-2026-1115/): Stored XSS in parisneo/lollms (critical 9.6)
- [CVE-2026-12228](https://insights.sbomify.com/CVE-2026-12228/): Stored XSS in Direct Messages via Prompt Sharing in parisneo/lollms (high 8.7)
- [CVE-2026-0562](https://insights.sbomify.com/CVE-2026-0562/): Insecure Direct Object Reference (IDOR) in parisneo/lollms (high 8.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-3121 and fix it if it is affected.

What it is: CVE-2024-3121 is a medium-severity command injection vulnerability in parisneo/lollms, published on 24 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-3121 exists.

Affected packages and fixed versions:
- lollms (PyPI): affected all versions up to 9.5.1; no fix listed
- lollms (PyPI): affected all versions up to 9.5.1; no fix listed
- lollms (PyPI): affected all versions up to 9.5.1; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-3121/ (Markdown: https://insights.sbomify.com/CVE-2024-3121/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-3121
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-3121
- OSV: https://osv.dev/vulnerability/CVE-2024-3121

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-3121/
Summaries are generated and may contain mistakes; the official description above is the record.