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

> Remote attackers can crash the Fersch Formbankserver daemon by sending multiple requests with path traversal sequences in the Name parameter.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 9 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6jpg-94h7-8x32

## What is CVE-2006-6910?

CVE-2006-6910 is a high-severity denial of service vulnerability in n/a, published on 9 Jan 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

formbankcgi.exe in Fersch Formbankserver 1.9, when the PATH_INFO begins with Abfrage, allows remote attackers to cause a denial of service (daemon crash) via multiple requests containing many /../ sequences in the Name parameter.

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

It affects 1 product.


Products: Fersch Formbankserver.

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

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

## Is CVE-2006-6910 being exploited?

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

Public exploit code:

- Formbankserver 1.9 - 'Name' Remote Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-0138](https://insights.sbomify.com/CVE-2007-0138/): Denial of service in n/a (medium 5.0)
- [CVE-2007-0055](https://insights.sbomify.com/CVE-2007-0055/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6910 is a high-severity denial of service vulnerability in n/a, published on 9 Jan 2007. 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-2006-6910 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-6910/ (Markdown: https://insights.sbomify.com/CVE-2006-6910/index.md)
```

## Sources

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

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