# CVE-2007-2010: Use after free in n/a

> Remote authenticated users can crash the bftpd daemon via double free in get or mget commands, causing denial of service.

- **Severity:** Medium 6.8 (`AV:N/AC:L/Au:S/C:N/I:N/A:C`)
- **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:** 12 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4vrm-366f-288x

## What is CVE-2007-2010?

CVE-2007-2010 is a medium-severity use after free vulnerability in n/a, published on 12 Apr 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Double free vulnerability in bftpd before 1.8 allows remote authenticated users to cause a denial of service (daemon crash) via a (1) get or (2) mget command.

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

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

It affects 1 product.


Products: Bftpd Bftpd.

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

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

## Is CVE-2007-2010 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-2051](https://insights.sbomify.com/CVE-2007-2051/): Memory corruption in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2010 is a medium-severity use after free vulnerability in n/a, published on 12 Apr 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-2010 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-2010/ (Markdown: https://insights.sbomify.com/CVE-2007-2010/index.md)
```

## Sources

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

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