# CVE-2023-35845: Security feature bypass in n/a

> Local attackers can bypass TLS certificate validation by modifying world-writable files in Anaconda or Miniconda installations.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2023
- **Updated:** 26 Sep 2024
- **Also known as:** BIT-miniconda-2023-35845, GHSA-hhfv-2xc3-52h6

## What is CVE-2023-35845?

CVE-2023-35845 is a medium-severity vulnerability in n/a, published on 11 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Anaconda 3 2023.03-1-Linux allows local users to disrupt TLS certificate validation by modifying the cacert.pem file used by the installed pip program. This occurs because many files are installed as world-writable on Linux, ignoring umask, even when these files are installed as root. Miniconda is also affected.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2023-35845?

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


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

Products: Anaconda Anaconda3.

## How do I fix CVE-2023-35845?

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

## Is CVE-2023-35845 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-42969](https://insights.sbomify.com/CVE-2021-42969/): Command injection in n/a (high 8.8)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-35845 and fix it if it is affected.

What it is: CVE-2023-35845 is a medium-severity vulnerability in n/a, published on 11 Sep 2023. 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-2023-35845 exists.

Affected packages and fixed versions:
- miniconda (Bitnami): affected from 2023.03-1.0 up to 2023.03-1.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-2023-35845/ (Markdown: https://insights.sbomify.com/CVE-2023-35845/index.md)
```

## Sources

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

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