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

> Remote attackers can cause denial of service via memory consumption by sending numerous SendNrlLink directives to WorkSite Web.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rfj9-gw43-8w26

## What is CVE-2008-1700?

CVE-2008-1700 is a high-severity denial of service vulnerability in n/a, published on 8 Apr 2008. It can be exploited over the network, with no action from the victim.

### Official description

The Web TransferCtrl Class 8,2,1,4 (iManFile.cab), as used in WorkSite Web 8.2 before SP1 P2, allows remote attackers to cause a denial of service (memory consumption) via a large number of SendNrlLink directives, which opens a separate window for each directive.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 1 product.


Products: Interwoven Worksite Web.

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

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

## Is CVE-2008-1700 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-1617](https://insights.sbomify.com/CVE-2008-1617/): Use after free in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-1700 is a high-severity denial of service vulnerability in n/a, published on 8 Apr 2008. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-1700 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-1700/ (Markdown: https://insights.sbomify.com/CVE-2008-1700/index.md)
```

## Sources

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

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