# CVE-2015-7665: Information disclosure in n/a

> Remote FTP servers can discover the Tor client IP address due to automatic fallback from passive to active FTP in Tails OS.

- **Severity:** Medium 5.3 (`CVSS:3.0/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:** Yes
- **Published:** 27 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mp83-q9h6-ghgh

## What is CVE-2015-7665?

CVE-2015-7665 is a medium-severity vulnerability in n/a, published on 27 Dec 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tails before 1.7 includes the wget program but does not prevent automatic fallback from passive FTP to active FTP, which allows remote FTP servers to discover the Tor client IP address by reading a (1) PORT or (2) EPRT command.  NOTE: within wget itself, the automatic fallback is not considered a vulnerability by CVE.

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

## Which versions are affected by CVE-2015-7665?

It affects 1 product.


Products: Tails Project Tails.

## How do I fix CVE-2015-7665?

Upgrade to a fixed version.

## Is CVE-2015-7665 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-7665 and fix it if it is affected.

What it is: CVE-2015-7665 is a medium-severity vulnerability in n/a, published on 27 Dec 2015. 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-2015-7665 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-2015-7665/ (Markdown: https://insights.sbomify.com/CVE-2015-7665/index.md)
```

## Sources

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

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