# CVE-2009-1675: Memory corruption in n/a

> Remote FTP servers can execute arbitrary code on ElectraSoft 32bit FTP clients via a stack-based buffer overflow in PASV reply handling.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 May 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8hj6-4wv2-39hh

## What is CVE-2009-1675?

CVE-2009-1675 is a critical memory corruption vulnerability in n/a, published on 18 May 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in ElectraSoft 32bit FTP 09.04.24 allows remote FTP servers to execute arbitrary code via a long 227 reply to a PASV command.

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

## Which versions are affected by CVE-2009-1675?

It affects 1 product.


Products: Electrasoft 32bit Ftp.

## How do I fix CVE-2009-1675?

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

## Is CVE-2009-1675 being exploited?

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

Public exploit code:

- 32bit FTP - 'PASV' Reply Client Remote Overflow (Metasploit) (exploitdb)
- 32bit FTP Client Stack Buffer Overflow  (metasploit)

## Other vulnerabilities in n/a

- [CVE-2009-1611](https://insights.sbomify.com/CVE-2009-1611/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-1592](https://insights.sbomify.com/CVE-2009-1592/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-1675 and fix it if it is affected.

What it is: CVE-2009-1675 is a critical memory corruption vulnerability in n/a, published on 18 May 2009. 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-2009-1675 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-2009-1675/ (Markdown: https://insights.sbomify.com/CVE-2009-1675/index.md)
```

## Sources

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

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