# CVE-2017-6465: Memory corruption in n/a

> A buffer overflow in FTPShell Client allows remote code execution when processing a malicious PWD response from an FTP server.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mq94-vm4p-fh7g

## What is CVE-2017-6465?

CVE-2017-6465 is a critical memory corruption vulnerability in n/a, published on 10 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Remote Code Execution was discovered in FTPShell Client 6.53. By default, the client sends a PWD command to the FTP server it is connecting to; however, it doesn't check the response's length, leading to a buffer overflow situation.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Ftpshell Ftpshell Client.

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

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

## Is CVE-2017-6465 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-6465 exists.

Public exploit code:

- FTPShell 5.1 Stack Buffer Overflow (metasploit)
- FTPShell Client 6.53 - Remote Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2018-7573](https://insights.sbomify.com/CVE-2018-7573/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6465 is a critical memory corruption vulnerability in n/a, published on 10 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-6465 exists.

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

## Sources

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

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