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

> A flaw in kdesktop_lock prevents the screensaver from activating or manual desktop locking, causing a denial of service for local users.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-m7h3-c7v2-v2cm, RHSA-2006:0576

## What is CVE-2006-2933?

CVE-2006-2933 is a medium-severity denial of service vulnerability in Kde Kde, published on 27 Jul 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

kdesktop_lock in kdebase before 3.1.3-5.11 for KDE in Red Hat Enterprise Linux (RHEL) 3 does not properly terminate, which can prevent the screensaver from activating or prevent users from manually locking the desktop.

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

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kdebase` | Red Hat:enterprise_linux:3::as | All versions | 6:3.1.3-5.11 |
| `kdebase-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 6:3.1.3-5.11 |
| `kdebase-devel` | Red Hat:enterprise_linux:3::as | All versions | 6:3.1.3-5.11 |
| `kdebase` | Red Hat:enterprise_linux:3::desktop | All versions | 6:3.1.3-5.11 |
| `kdebase-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 6:3.1.3-5.11 |
| `kdebase-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 6:3.1.3-5.11 |
| `kdebase` | Red Hat:enterprise_linux:3::es | All versions | 6:3.1.3-5.11 |
| `kdebase-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 6:3.1.3-5.11 |
| `kdebase-devel` | Red Hat:enterprise_linux:3::es | All versions | 6:3.1.3-5.11 |
| `kdebase` | Red Hat:enterprise_linux:3::ws | All versions | 6:3.1.3-5.11 |
| `kdebase-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 6:3.1.3-5.11 |
| `kdebase-devel` | Red Hat:enterprise_linux:3::ws | All versions | 6:3.1.3-5.11 |

Products: Kde Kde, Redhat Enterprise Linux, Redhat Enterprise Linux Desktop.

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

Apply the vendor's patch.

## Is CVE-2006-2933 being exploited?

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

## Other vulnerabilities in Kde Kde

- [CVE-2005-0011](https://insights.sbomify.com/CVE-2005-0011/): Memory corruption in n/a (critical 10.0)
- [CVE-2003-0690](https://insights.sbomify.com/CVE-2003-0690/): Privilege escalation in n/a (critical 10.0)
- [CVE-2008-1670](https://insights.sbomify.com/CVE-2008-1670/): Memory corruption in n/a (critical 9.3)
- [CVE-2012-4512](https://insights.sbomify.com/CVE-2012-4512/): Memory corruption in Konqueror (high 8.8)
- [CVE-2006-0019](https://insights.sbomify.com/CVE-2006-0019/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2933 is a medium-severity denial of service vulnerability in Kde Kde, published on 27 Jul 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-2933 in the wild and no public exploit code.

Affected product: Kde Kde. 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-2933/ (Markdown: https://insights.sbomify.com/CVE-2006-2933/index.md)
```

## Sources

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

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