# CVE-2008-6829: Denial of service in n/a

> Remote attackers can crash VicFTPS server by sending a malformed LIST command, causing denial of service.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-48p8-rpvf-qgx2

## What is CVE-2008-6829?

CVE-2008-6829 is a medium-severity denial of service vulnerability in n/a, published on 8 Jun 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

VicFTPS 5.0 allows remote attackers to cause a denial of service (crash) via a LIST command that starts with a "/\/" (forward slash, backward slash, forward slash).  NOTE: this might be the same issue as CVE-2008-2031.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Vicftps Vicftps.

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

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

## Is CVE-2008-6829 being exploited?

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

Public exploit code:

- vicFTP 5.0 - 'LIST' Remote Denial of Service (exploitdb)
- Victory FTP Server 5.0 LIST DoS (metasploit)

## Other vulnerabilities in n/a

- [CVE-2007-1014](https://insights.sbomify.com/CVE-2007-1014/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-2031](https://insights.sbomify.com/CVE-2008-2031/): Null dereference in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-6829 is a medium-severity denial of service vulnerability in n/a, published on 8 Jun 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-2008-6829 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-2008-6829/ (Markdown: https://insights.sbomify.com/CVE-2008-6829/index.md)
```

## Sources

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

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