# CVE-2006-6624: Denial of service in n/a

> Authenticated remote attackers can crash the Sambar Server FTP service by sending a long series of directory traversal sequences in the SIZE command.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:N/A:P`)
- **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:** 18 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mmxr-v8q7-833m

## What is CVE-2006-6624?

CVE-2006-6624 is a medium-severity denial of service vulnerability in n/a, published on 18 Dec 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The FTP Server in Sambar Server 6.4 allows remote authenticated users to cause a denial of service (application crash) via a long series of "./" sequences in the SIZE command.

## Which versions are affected by CVE-2006-6624?

It affects 1 product.


Products: Sambar Sambar Server.

## How do I fix CVE-2006-6624?

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

## Is CVE-2006-6624 being exploited?

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

Public exploit code:

- Sambar FTP Server 6.4 - 'SIZE' Remote Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2000-0509](https://insights.sbomify.com/CVE-2000-0509/): Memory corruption in n/a (critical 10.0)
- [CVE-2003-1286](https://insights.sbomify.com/CVE-2003-1286/): Server-side request forgery in n/a (high 7.5)
- [CVE-2001-1106](https://insights.sbomify.com/CVE-2001-1106/): Weak cryptography in n/a (high 7.5)
- [CVE-2002-0128](https://insights.sbomify.com/CVE-2002-0128/): Memory corruption in n/a (high 7.5)
- [CVE-2001-1292](https://insights.sbomify.com/CVE-2001-1292/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-6624 and fix it if it is affected.

What it is: CVE-2006-6624 is a medium-severity denial of service vulnerability in n/a, published on 18 Dec 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6624 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-2006-6624/ (Markdown: https://insights.sbomify.com/CVE-2006-6624/index.md)
```

## Sources

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

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