CVE-2015-8025
driver/subprocs.c in XScreenSaver before 5.34 does not properly perfor ...
Overview
Description
driver/subprocs.c in XScreenSaver before 5.34 does not properly perform an internal consistency check, which allows physically proximate attackers to bypass the lock screen by hot swapping monitors.
Source: OX vulnerability database
Severity
2.1 · LOW
CVSS 2.0 base score, scored by NVD.
- Access vector
- Local
- Access complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
AV:L/AC:L/Au:N/C:N/I:P/A:N
Weakness: CWE-264
Affected packages · 0
No registry package. This ID affects operating system packages only.
Operating systems · 6 fixes
debian 4 releases · 1 package
fixed 4
xscreensaver
| Release | Package | Fixed in |
|---|---|---|
| 11 | xscreensaver | 5.34-1 |
| 12 | xscreensaver | 5.34-1 |
| 13 | xscreensaver | 5.34-1 |
| 14 | xscreensaver | 5.34-1 |
echo 1 release · 1 package
fixed 1
xscreensaver
| Release | Package | Fixed in |
|---|---|---|
| xscreensaver | 5.34-1 |
openSUSE 1 release · 1 package
fixed 1
xscreensaver
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Tumbleweed | xscreensaver +2 | 5.34-1.6 | openSUSE-SU-2024:10216-1 |
References
- lists.opensuse.org http://lists.opensuse.org/opensuse-updates/2015-11/msg00102.html
- www.debian.org http://www.debian.org/security/2016/dsa-3438
- www.openwall.com http://www.openwall.com/lists/oss-security/2015/10/24/2
- www.openwall.com http://www.openwall.com/lists/oss-security/2015/10/25/1
- www.openwall.com http://www.openwall.com/lists/oss-security/2015/10/29/12
- www.oracle.com http://www.oracle.com/technetwork/topics/security/bulletinjul2016-3090568.html
- www.securitytracker.com http://www.securitytracker.com/id/1034052
- www.ubuntu.com http://www.ubuntu.com/usn/USN-2789-1
- twitter.com https://twitter.com/Thaolia/status/656823859304398848
- ubuntu.com https://ubuntu.com/security/notices/USN-2789-1
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.