# CVE-2015-8025: Security feature bypass in n/a

> Physically proximate attackers can bypass the XScreenSaver lock screen by hot swapping monitors due to a missing internal consistency check.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Nov 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-8025, DLA-338-1, DSA-3438-1, GHSA-gfx7-7vxh-f4g8, MGASA-2015-0431, SUSE-SU-2015:2053-1, SUSE-SU-2015:2053-2, SUSE-SU-2015:2054-1, UBUNTU-CVE-2015-8025, openSUSE-SU-2024:10216-1

## What is CVE-2015-8025?

CVE-2015-8025 is a low-severity vulnerability in Canonical Ubuntu Linux, published on 10 Nov 2015. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-264

## Which versions are affected by CVE-2015-8025?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `xscreensaver` | SUSE:Linux Enterprise Desktop 11 SP3 | All versions | 5.07-6.36.1 |
| `xscreensaver` | SUSE:Linux Enterprise Desktop 11 SP4 | All versions | 5.07-6.36.1 |
| `xscreensaver` | SUSE:Linux Enterprise Desktop 12 | All versions | 5.22-7.1 |
| `xscreensaver` | SUSE:Linux Enterprise Desktop 12 SP1 | All versions | 5.22-7.1 |
| `xscreensaver` | SUSE:Linux Enterprise Server 11 SP3 | All versions | 5.07-6.36.1 |
| `xscreensaver` | SUSE:Linux Enterprise Server 11 SP3-TERADATA | All versions | 5.07-6.36.1 |
| `xscreensaver` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 5.07-6.36.1 |
| `xscreensaver` | SUSE:Linux Enterprise Server 12 | All versions | 5.22-7.1 |
| `xscreensaver` | SUSE:Linux Enterprise Server 12 SP1 | All versions | 5.22-7.1 |
| `xscreensaver` | SUSE:Linux Enterprise Server for SAP Applications 11 SP3 | All versions | 5.07-6.36.1 |
| `xscreensaver` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 5.07-6.36.1 |
| `xscreensaver` | SUSE:Linux Enterprise Server for SAP Applications 12 | All versions | 5.22-7.1 |
| `xscreensaver` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 5.22-7.1 |
| `xscreensaver` | openSUSE:Tumbleweed | All versions | 5.34-1.6 |

Products: Canonical Ubuntu Linux, Xscreensaver Project Xscreensaver.

## How do I fix CVE-2015-8025?

Upgrade to a fixed version.

## Is CVE-2015-8025 being exploited?

There is no known exploitation of CVE-2015-8025 in the wild and no public exploit code.

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-8025 and fix it if it is affected.

What it is: CVE-2015-8025 is a low-severity vulnerability in Canonical Ubuntu Linux, published on 10 Nov 2015. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-8025 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-8025/ (Markdown: https://insights.sbomify.com/CVE-2015-8025/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-8025
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-8025
- OSV: https://osv.dev/vulnerability/CVE-2015-8025

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-8025/
Summaries are generated and may contain mistakes; the official description above is the record.