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

> Unauthenticated attackers can retrieve arbitrary files from Goldshell ASIC miners via a path traversal vulnerability.

- **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:** 20 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-3gw8-89v6-jfv4

## What is CVE-2022-24659?

CVE-2022-24659 is a high-severity path traversal vulnerability in n/a, published on 20 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Goldshell ASIC Miners v2.2.1 and below was discovered to contain a path traversal vulnerability which allows unauthenticated attackers to retrieve arbitrary files from the device.

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

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

It affects 1 product.


Products: Goldshell Goldshell Miner Firmware.

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

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

## Is CVE-2022-24659 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-24657](https://insights.sbomify.com/CVE-2022-24657/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2022-24660](https://insights.sbomify.com/CVE-2022-24660/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24659 is a high-severity path traversal vulnerability in n/a, published on 20 Jul 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-24659 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-24659/ (Markdown: https://insights.sbomify.com/CVE-2022-24659/index.md)
```

## Sources

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

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