xlockmore vulnerabilities and fixes

Recent CVEs affecting xlockmore, with upgrade or downgrade steps. 3 tracked.

xlockmore has 3 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 1. Most recent: 2019-11-21. Highest priority: CVE-2006-0061 (score 64/100).

• CVE-2012-4524 HIGH 7.5 UPGRADE MITIGATE xlockmore before 5.43 'dclock' security bypass vulnerability
• CVE-2006-0062 CRITICAL 9.8 DOWNGRADE xlockmore 5.13 allows potential xlock bypass when FVWM switches to the same virtual desktop as a new Gaim wind
• CVE-2006-0061 CRITICAL 9.8 DOWNGRADE xlockmore 5.13 and 5.22 segfaults when using libpam-opensc and returns the underlying xsession

FAQ

How do I fix xlockmore vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is xlockmore being exploited right now?

None of the tracked xlockmore CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which xlockmore CVE should I patch first?

CVE-2006-0061 currently ranks highest (64/100): xlockmore 5.13 and 5.22 segfaults when using libpam-opensc and returns the underlying xsession.

RSS feed for xlockmore · ← Back to latest CVEs