xscreensaver vulnerabilities and fixes
Recent CVEs affecting xscreensaver, with upgrade or downgrade steps. 4 tracked.
xscreensaver has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2021-06-10. Highest priority: CVE-2011-2187 (score 48/100).
- CVE-2021-34557 MEDIUM 4.6 DOWNGRADE MITIGATE XScreenSaver 5.45 can be bypassed if the machine has more than ten disconnectable video outputs
- CVE-2021-31523 HIGH 7.8 MITIGATE The Debian xscreensaver 5.42+dfsg1-1 package for XScreenSaver has cap_net_raw enabled for the /usr/libexec/xsc
- CVE-2015-8025 LOW 2.1 MITIGATE DOWNGRADE driver/subprocs.c in XScreenSaver before 5.34 does not properly perform an internal consistency check, which a
- CVE-2011-2187 HIGH 7.8 UPGRADE MITIGATE xscreensaver before 5.14 crashes during activation and leaves the screen unlocked when in Blank Only Mode and
FAQ
How do I fix xscreensaver 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 xscreensaver being exploited right now?
None of the tracked xscreensaver CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which xscreensaver CVE should I patch first?
CVE-2011-2187 currently ranks highest (48/100): xscreensaver before 5.14 crashes during activation and leaves the screen unlocked when in Blank Only Mode and .