# CVE-2022-35861: Path traversal in n/a

> Local attackers can escalate privileges and execute arbitrary code by crafting a malicious .python-version file in the current directory.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** Yes
- **Published:** 17 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-7rf7-7xf5-v9v3, openSUSE-SU-2022:10183-1, openSUSE-SU-2024:12200-1

## What is CVE-2022-35861?

CVE-2022-35861 is a high-severity path traversal vulnerability in n/a, published on 17 Jul 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

pyenv 1.2.24 through 2.3.2 allows local users to gain privileges via a .python-version file in the current working directory. An attacker can craft a Python version string in .python-version to execute shims under their control. (Shims are executables that pass a command along to a specific version of pyenv. The version string is used to construct the path to the command, and there is no validation of whether the version specified is a valid version. Thus, relative path traversal can occur.)

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2022-35861?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pyenv` | SUSE:Package Hub 15 SP4 | All versions | 2.3.5-bp154.2.3.1 |
| `pyenv` | openSUSE:Leap 15.4 | All versions | 2.3.5-bp154.2.3.1 |

Products: Pyenv Pyenv.

## How do I fix CVE-2022-35861?

Upgrade to a fixed version.

## Is CVE-2022-35861 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-35861 and fix it if it is affected.

What it is: CVE-2022-35861 is a high-severity path traversal vulnerability in n/a, published on 17 Jul 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-35861 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2022-35861/ (Markdown: https://insights.sbomify.com/CVE-2022-35861/index.md)
```

## Sources

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

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