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

> An attacker can write files to arbitrary directories via the dumpwallet RPC, potentially violating security models in forks.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jan 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-xvf3-hffw-q8j7, openSUSE-SU-2022:0072-1

## What is CVE-2021-3195?

CVE-2021-3195 is a high-severity path traversal vulnerability in Bitcoin Bitcoin Core, published on 21 Jan 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

bitcoind in Bitcoin Core through 0.21.0 can create a new file in an arbitrary directory (e.g., outside the ~/.bitcoin directory) via a dumpwallet RPC call. NOTE: this reportedly does not violate the security model of Bitcoin Core, but can violate the security model of a fork that has implemented dumpwallet restrictions

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bitcoin` | SUSE:Package Hub 15 SP3 | All versions | 0.21.2-bp153.2.3.1 |
| `bitcoin` | openSUSE:Leap 15.3 | All versions | 0.21.2-bp153.2.3.1 |

Products: Bitcoin Bitcoin Core.

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

Apply the vendor's patch.

## Is CVE-2021-3195 being exploited?

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

## Other vulnerabilities in Bitcoin Bitcoin Core

- [CVE-2025-46597](https://insights.sbomify.com/CVE-2025-46597/): Integer overflow in n/a (high 7.5)
- [CVE-2025-54604](https://insights.sbomify.com/CVE-2025-54604/): Denial of service in n/a (high 7.5)
- [CVE-2025-54605](https://insights.sbomify.com/CVE-2025-54605/): Denial of service in n/a (high 7.5)
- [CVE-2019-25220](https://insights.sbomify.com/CVE-2019-25220/): Denial of service in n/a (high 7.5)
- [CVE-2024-52912](https://insights.sbomify.com/CVE-2024-52912/): Integer overflow in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-3195 is a high-severity path traversal vulnerability in Bitcoin Bitcoin Core, published on 21 Jan 2021. 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-2021-3195 in the wild and no public exploit code.

Affected product: Bitcoin Bitcoin Core. 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-3195/ (Markdown: https://insights.sbomify.com/CVE-2021-3195/index.md)
```

## Sources

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

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