Sillycycle Xlockmore

3 CVEs affecting Sillycycle Xlockmore. Latest disclosed: 2019-11-21. Critical: 2, High: 1.

Top CVEs affecting Sillycycle Xlockmore
CVESeverityScorePublishedSummary
CVE-2006-0062Critical9.82019-11-06xlockmore 5.13 allows potential xlock bypass when FVWM switches to the same virtual desktop as a new Gaim window.
CVE-2006-0061Critical9.82019-11-06xlockmore 5.13 and 5.22 segfaults when using libpam-opensc and returns the underlying xsession. This allows unauthorized users access to the X session.
CVE-2012-4524High7.52019-11-21xlockmore before 5.43 'dclock' security bypass vulnerability