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

> Remote attackers can crash applications using libkhtml, such as Konqueror and KMail, by sending malformed HTML tags, requiring user interaction to view the content.

- **Severity:** Medium 4.3 (`AV:N/AC:M/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vr7j-65g3-xc3f

## What is CVE-2006-6660?

CVE-2006-6660 is a medium-severity denial of service vulnerability in n/a, published on 20 Dec 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The nodeType function in KDE libkhtml 4.2.0 and earlier, as used by Konquerer, KMail, and other programs, allows remote attackers to cause a denial of service (crash) via malformed HTML tags, possibly involving a COL SPAN tag embedded in a RANGE tag.

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

It affects 1 product.


Products: Kde Libkhtml.

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

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

## Is CVE-2006-6660 being exploited?

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

Public exploit code:

- KDE LibkHTML 4.2 - NodeType Function Denial of Service (exploitdb)
- KDE libkhtml 3.5 < 4.2.0 - Unhandled HTML Parse Exception (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6660 is a medium-severity denial of service vulnerability in n/a, published on 20 Dec 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6660 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-6660/ (Markdown: https://insights.sbomify.com/CVE-2006-6660/index.md)
```

## Sources

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

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