CVE-2006-2933 json
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…
published 2006-07-27 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-2930
- cvss
- 4.6
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 34%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2006-2933 updated
security flaw
-
Red Hat Desktop version 3 kdebase 3.1.3-5.11 Red Hat Enterprise Linux AS version 3 kdebase 3.1.3-5.11 Red Hat Enterprise Linux ES version 3 kdebase 3.1.3-5.11 Red Hat Enterprise Linux WS version 3 kdebase 3.1.3-5.11fixed: vendor fix RHSA-2006:0576
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.6 | AV:L/AC:L/Au:N/C:P/I:P/A:P |
References
-
secunia.com
/advisories/21203
third-party-advisory, patch, vendor-advisory
-
redhat.com
/support/errata/RHSA-2006-0576.html
vendor-advisory
- bugzilla.redhat.com /bugzilla/show_bug.cgi?id=177755
-
securitytracker.com
/id?1016571
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10535
vdb-entry, signature
-
securityfocus.com
/bid/19152
vdb-entry
Sources
- CVE List CVE-2006-2933
- NVD CVE-2006-2933
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.