Skip to content
Fencer Vulns
medium 6.8

CVE-2007-4569 json

backend/session.c in KDM in KDE 3.3.0 through 3.5.7, when autologin is configured and "shutdown with password" is enabled, allows remote at…

published 2007-09-21 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-4551

cvss
6.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits
0
none known

Summary

backend/session.c in KDM in KDE 3.3.0 through 3.5.7, when autologin is configured and "shutdown with password" is enabled, allows remote attackers to bypass the password requirement and login to arbitrary accounts via unspecified vectors.

Patch / fix

  • kdebase RHEL 4 6:3.3.1-6.el4
  • kdebase RHEL 5 6:3.5.4-15.el5

red hat advisories RHSA-2007:0905

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-2007-4569 updated

kdm password-less login vulnerability

  • Red Hat Enterprise Linux (v. 5 server) kdebase 3.5.4-15.el5 Red Hat Enterprise Linux AS version 4 kdebase 3.3.1-6.el4 Red Hat Enterprise Linux Desktop (v. 5 client) kdebase 3.5.4-15.el5 Red Hat Enterprise Linux Desktop version 4 kdebase 3.3.1-6.el4 Red Hat Enterprise Linux Desktop Workstation (v. 5 client) kdebase 3.5.4-15.el5 Red Hat Enterprise Linux ES version 4 kdebase 3.3.1-6.el4
    +1 more products
    Red Hat Enterprise Linux WS version 4 kdebase 3.3.1-6.el4
    fixed: vendor fix RHSA-2007:0905

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

1.01% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 6.8 AV:L/AC:L/Au:S/C:C/I:C/A:C

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

References

Sources

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.