# CVE-2007-1485: Memory corruption in n/a

> Local attackers can execute arbitrary code via a buffer overflow in QFTP's set_umask function, though exploitation is disputed due to lack of setuid privileges.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fvxv-mcmq-2qq6

## What is CVE-2007-1485?

CVE-2007-1485 is a critical memory corruption vulnerability in n/a, published on 16 Mar 2007. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in the set_umask function in QFTP in LIBFtp 3.1-1 allows local users to execute arbitrary code via a long -m argument. NOTE: CVE disputes this issue because QFTP is not setuid, and it is unlikely that there are web interfaces to QFTP that would accept untrusted command line arguments

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

It affects 1 product.


Products: Ftplib Ftplib.

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

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

## Is CVE-2007-1485 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-1485 is a critical memory corruption vulnerability in n/a, published on 16 Mar 2007. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-1485 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-2007-1485/ (Markdown: https://insights.sbomify.com/CVE-2007-1485/index.md)
```

## Sources

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

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