David Bagley Xlock

2 CVEs affecting David Bagley Xlock. Latest disclosed: 2000-10-20. Critical: 0, High: 0.

Top CVEs affecting David Bagley Xlock
CVESeverityScorePublishedSummary
CVE-2000-07632000-10-20xlockmore and xlockf do not properly cleanse user-injected format strings, which allows local users to gain root privileges via the -d option.
CVE-2000-04552000-05-29Buffer overflow in xlockmore xlock program version 4.16 and earlier allows local users to read sensitive data from memory via a long -mode option.