# CVE-2008-0725: Memory corruption in n/a

> Remote attackers can cause denial of service or potentially execute arbitrary code via heap-based buffer overflows in Titan FTP Server.

- **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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Feb 2008
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-79j3-hc9x-7c9p

## What is CVE-2008-0725?

CVE-2008-0725 is a critical memory corruption vulnerability in n/a, published on 12 Feb 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple heap-based buffer overflows in the (1) FTP service and (2) administration service in Titan FTP Server 6.0.5.549 allow remote attackers to cause a denial of service (daemon hang) and possibly execute arbitrary code via a long command.  NOTE: the USER and PASS commands for the FTP service are covered by CVE-2008-0702.

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

## Which versions are affected by CVE-2008-0725?

It affects 1 product.


Products: Titan Ftp Server.

## How do I fix CVE-2008-0725?

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

## Is CVE-2008-0725 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-0725 and fix it if it is affected.

What it is: CVE-2008-0725 is a critical memory corruption vulnerability in n/a, published on 12 Feb 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-0725 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-2008-0725/ (Markdown: https://insights.sbomify.com/CVE-2008-0725/index.md)
```

## Sources

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

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