# CVE-2010-4871: Denial of service in n/a

> Attackers can cause a denial of service in SmartFTP by sending a long filename, requiring users to upgrade to a patched version.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 7 Oct 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p7vx-368h-q3qh

## What is CVE-2010-4871?

CVE-2010-4871 is a critical denial of service vulnerability in n/a, published on 7 Oct 2011. It can be exploited over the network.

### Official description

Unspecified vulnerability in SmartFTP before 4.0 Build 1142 allows attackers to have an unknown impact via a long filename.

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

It affects 1 product.


Products: Smartftp Smartftp.

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

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

## Is CVE-2010-4871 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-3099](https://insights.sbomify.com/CVE-2010-3099/): Path traversal in n/a (critical 9.3)
- [CVE-2003-1319](https://insights.sbomify.com/CVE-2003-1319/): Memory corruption in n/a (high 7.6)
- [CVE-2007-0790](https://insights.sbomify.com/CVE-2007-0790/): Memory corruption in n/a (high 7.5)
- [CVE-2018-25234](https://insights.sbomify.com/CVE-2018-25234/): SmartFTP Client 9.0.2615.0 Denial of Service via Host Field (medium 6.9)
- [CVE-2010-5219](https://insights.sbomify.com/CVE-2010-5219/): Path traversal in n/a (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-4871 is a critical denial of service vulnerability in n/a, published on 7 Oct 2011. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2010-4871 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-2010-4871/ (Markdown: https://insights.sbomify.com/CVE-2010-4871/index.md)
```

## Sources

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

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