# CVE-2014-1949: Auth bypass in n/a

> Physically proximate attackers can bypass the lock screen in GTK+ based screensavers by pressing the menu button.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 16 Jan 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-1949, GHSA-38gw-6g45-69p7, MGASA-2014-0374, UBUNTU-CVE-2014-1949

## What is CVE-2014-1949?

CVE-2014-1949 is a high-severity authentication bypass vulnerability in n/a, published on 16 Jan 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

GTK+ 3.10.9 and earlier, as used in cinnamon-screensaver, gnome-screensaver, and other applications, allows physically proximate attackers to bypass the lock screen by pressing the menu button.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2014-1949?

It affects 3 products.


Products: Canonical Ubuntu, Gnome Gtk, Linuxmint Linux Mint.

## How do I fix CVE-2014-1949?

Upgrade to a fixed version.

## Is CVE-2014-1949 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-1424](https://insights.sbomify.com/CVE-2014-1424/): Security feature bypass in n/a (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-1949 and fix it if it is affected.

What it is: CVE-2014-1949 is a high-severity authentication bypass vulnerability in n/a, published on 16 Jan 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-2014-1949 in the wild and no public exploit code.

Affected product: n/a. 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-2014-1949/ (Markdown: https://insights.sbomify.com/CVE-2014-1949/index.md)
```

## Sources

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

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