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

> Attackers can list directories via path traversal in the awful-salmonella-tar library due to missing safe-path checks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 18 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-2vjx-96pr-9r8r

## What is CVE-2022-25358?

CVE-2022-25358 is a medium-severity path traversal vulnerability in n/a, published on 18 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A ..%2F path traversal vulnerability exists in the path handler of awful-salmonella-tar before 0.0.4. Attackers can only list directories (not read files). This occurs because the safe-path? Scheme predicate is not used for directories.

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

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

It affects 1 product.


Products: Awful-Salmonella-Tar Project Awful-Salmonella-Tar.

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

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

## Is CVE-2022-25358 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-25358 is a medium-severity path traversal vulnerability in n/a, published on 18 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-25358 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-25358/ (Markdown: https://insights.sbomify.com/CVE-2022-25358/index.md)
```

## Sources

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

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