# CVE-2017-15269: Server-side request forgery in n/a

> Attackers can use the FTP server to perform bounce scans, bypassing network restrictions and potentially probing internal systems.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-w5qc-2wh9-55pc

## What is CVE-2017-15269?

CVE-2017-15269 is a medium-severity server-side request forgery vulnerability in n/a, published on 15 Nov 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The PSFTPd 10.0.4 Build 729 server does not prevent FTP bounce scans by default. These can be performed using "nmap -b" and allow performing scans via the FTP server.

Weakness: CWE-610 (Externally Controlled Reference to a Resource in Another Sphere)

## Which versions are affected by CVE-2017-15269?

It affects 1 product.


Products: Psftp Psftpd.

## How do I fix CVE-2017-15269?

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

## Is CVE-2017-15269 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-15271](https://insights.sbomify.com/CVE-2017-15271/): Use after free in n/a (medium 5.9)
- [CVE-2017-15270](https://insights.sbomify.com/CVE-2017-15270/): Other in n/a (medium 5.3)
- [CVE-2017-15272](https://insights.sbomify.com/CVE-2017-15272/): Hardcoded credentials in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15269 and fix it if it is affected.

What it is: CVE-2017-15269 is a medium-severity server-side request forgery vulnerability in n/a, published on 15 Nov 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-15269 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-2017-15269/ (Markdown: https://insights.sbomify.com/CVE-2017-15269/index.md)
```

## Sources

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

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