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

> Attackers can cause a denial of service via infinite loop in Getahead Direct Web Remoting library using crafted input.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 11 Jan 2007
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-r4q2-fwqx-hjm5

## What is CVE-2006-6916?

CVE-2006-6916 is a high-severity denial of service vulnerability in n/a, published on 11 Jan 2007. It can be exploited over the network.

### Official description

Getahead Direct Web Remoting (DWR) before 1.1.3 allows attackers to cause a denial of service (infinite loop) via unknown vectors related to "crafted input."

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

It affects 1 product.


Products: Getahead Direct Web Remoting.

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

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

## Is CVE-2006-6916 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0184](https://insights.sbomify.com/CVE-2007-0184/): Incorrect Authorization in Getahead Direct Web Remoting (high 7.5)
- [CVE-2007-2377](https://insights.sbomify.com/CVE-2007-2377/): Information disclosure in n/a (medium 5.0)
- [CVE-2007-0185](https://insights.sbomify.com/CVE-2007-0185/): Direct Web Remoting vulnerable to Denial of Service (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6916 is a high-severity denial of service vulnerability in n/a, published on 11 Jan 2007. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2006-6916 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-2006-6916/ (Markdown: https://insights.sbomify.com/CVE-2006-6916/index.md)
```

## Sources

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

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