# CVE-2007-5201: FTP backend for Duplicity Discloses Passwords to Process Listing

> Local attackers can read FTP passwords from process arguments in Duplicity, exposing sensitive credentials.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 4 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-5201, GHSA-wxcw-rqxc-hj85, PYSEC-2026-633

## What is CVE-2007-5201?

CVE-2007-5201 is a medium-severity vulnerability in n/a, published on 4 Oct 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The FTP backend for Duplicity before 0.4.9 sends the password as a command line argument when calling ncftp, which might allow local users to read the password by listing the process and its arguments.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2007-5201?

3 open source packages ship an affected version, including duplicity. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `duplicity` | PyPI | All versions | 0.4.9 |
| `duplicity` | PyPI | All versions | 0.4.9 |
| `duplicity` | PyPI | All versions | 0.4.9 |

Products: Duplicity Project Duplicity.

## How do I fix CVE-2007-5201?

Upgrade duplicity to 0.4.9 or later.

## Is CVE-2007-5201 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5201 and fix it if it is affected.

What it is: CVE-2007-5201 is a medium-severity vulnerability in n/a, published on 4 Oct 2007. 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-2007-5201 in the wild and no public exploit code.

Affected packages and fixed versions:
- duplicity (PyPI): affected all versions; fixed in 0.4.9
- duplicity (PyPI): affected all versions; fixed in 0.4.9
- duplicity (PyPI): affected all versions; fixed in 0.4.9

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

## Sources

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

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