# CVE-2021-43495: Path traversal in n/a

> A directory traversal flaw in AlquistManager allows attackers to read critical system secrets, potentially facilitating remote code execution.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Nov 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hwpm-fghj-2p7p

## What is CVE-2021-43495?

CVE-2021-43495 is a high-severity path traversal vulnerability in n/a, published on 15 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AlquistManager branch as of commit 280d99f43b11378212652e75f6f3159cde9c1d36 is affected by a directory traversal vulnerability in alquist/IO/input.py. This attack can cause the disclosure of critical secrets stored anywhere on the system and can significantly aid in getting remote code access.

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

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

It affects 1 product.


Products: Alquistai Alquist.

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

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

## Is CVE-2021-43495 being exploited?

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

Public exploit code:

- AlquistManager Local File Inclusion (nuclei): http/cves/2021/CVE-2021-43495.yaml

## Other vulnerabilities in n/a

- [CVE-2021-43492](https://insights.sbomify.com/CVE-2021-43492/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-43495 is a high-severity path traversal vulnerability in n/a, published on 15 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-43495 exists.

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

## Sources

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

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