# SUSE-SU-2015:0803-1: Security update for gdm

> An authentication bypass in GDM allows local attackers to unlock the screen without credentials if fingerprint support is enabled.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Mar 2015

## What is SUSE-SU-2015:0803-1?

SUSE-SU-2015:0803-1 is an authentication bypass vulnerability in gdm, published on 11 Mar 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The GNOME Display Manager was updated to fix several bugs:

Security issue fixed:
- Removed gdm-fingerprint and gdm-smartcard pamfiles that allowed unlocking the screen without password or fingerprint if fingerprint reader support was enabled. (boo#900836).

Bugs fixed:
- Fix support for DISPLAYMANAGER_STARTS_XSERVER from /etc/sysconfig/displaymanager (bsc#919723).
- Ensure ShowLocalGreeter configuration key is properly handled (bgo#743440).

## Which versions are affected by SUSE-SU-2015:0803-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gdm` | SUSE:Linux Enterprise Desktop 12 | All versions | 3.10.0.1-16.1 |
| `gdm` | SUSE:Linux Enterprise Server 12 | All versions | 3.10.0.1-16.1 |
| `gdm` | SUSE:Linux Enterprise Server for SAP Applications 12 | All versions | 3.10.0.1-16.1 |
| `gdm` | SUSE:Linux Enterprise Software Development Kit 12 | All versions | 3.10.0.1-16.1 |

## How do I fix SUSE-SU-2015:0803-1?

Apply the vendor's patch.

## Is SUSE-SU-2015:0803-1 being exploited?

There is no known exploitation of SUSE-SU-2015:0803-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2015:0803-1 and fix it if it is affected.

What it is: SUSE-SU-2015:0803-1 is an authentication bypass vulnerability in gdm, published on 11 Mar 2015. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2015:0803-1 in the wild and no public exploit code.

Affected product: gdm. 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/SUSE-SU-2015-0803-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2015-0803-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2015:0803-1

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