# CVE-2021-42969: Command injection in n/a

> Attackers can execute arbitrary OS commands by writing to usercustomize.py, which runs when users activate Anaconda or open a terminal.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 May 2022
- **Updated:** 4 Aug 2024
- **Also known as:** BIT-miniconda-2021-42969, GHSA-p9v4-8gqg-fmcp

## What is CVE-2021-42969?

CVE-2021-42969 is a high-severity command injection vulnerability in n/a, published on 13 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Certain Anaconda3 2021.05 are affected by OS command injection. When a user installs Anaconda, an attacker can create a new file and write something in usercustomize.py. When the user opens the terminal or activates Anaconda, the command will be executed.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2021-42969?

1 open source package ship an affected version, including miniconda. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `miniconda` | Bitnami | From 2021.05.0 to 2021.05.0 | None |

Products: Anaconda Anaconda3.

## How do I fix CVE-2021-42969?

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

## Is CVE-2021-42969 being exploited?

There is no known exploitation of CVE-2021-42969 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2024-46060](https://insights.sbomify.com/CVE-2024-46060/): Privilege escalation in n/a (high 7.8)
- [CVE-2022-26526](https://insights.sbomify.com/CVE-2022-26526/): Privilege escalation in n/a (high 7.8)
- [CVE-2023-35845](https://insights.sbomify.com/CVE-2023-35845/): Security feature bypass in n/a (medium 4.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-42969 and fix it if it is affected.

What it is: CVE-2021-42969 is a high-severity command injection vulnerability in n/a, published on 13 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-42969 in the wild and no public exploit code.

Affected packages and fixed versions:
- miniconda (Bitnami): affected from 2021.05.0 up to 2021.05.0; 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-2021-42969/ (Markdown: https://insights.sbomify.com/CVE-2021-42969/index.md)
```

## Sources

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

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