# CVE-2015-3213: Auth bypass in n/a

> Physically proximate attackers can bypass the lock screen using specific mouse or touch gestures in the Clutter library.

- **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:** 12 Aug 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-3213, GHSA-57jc-p7pw-gpx8, RHSA-2015:1510

## What is CVE-2015-3213?

CVE-2015-3213 is a high-severity authentication bypass vulnerability in n/a, published on 12 Aug 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

The gesture handling code in Clutter before 1.16.2 allows physically proximate attackers to bypass the lock screen via certain (1) mouse or (2) touch gestures.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `clutter` | Red Hat:enterprise_linux:7::client | All versions | 0:1.14.4-12.el7_1.1 |
| `clutter-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:1.14.4-12.el7_1.1 |
| `clutter-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:1.14.4-12.el7_1.1 |
| `clutter-doc` | Red Hat:enterprise_linux:7::client | All versions | 0:1.14.4-12.el7_1.1 |
| `clutter` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.14.4-12.el7_1.1 |
| `clutter-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.14.4-12.el7_1.1 |
| `clutter-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.14.4-12.el7_1.1 |
| `clutter-doc` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.14.4-12.el7_1.1 |
| `clutter` | Red Hat:enterprise_linux:7::server | All versions | 0:1.14.4-12.ael7b_1.1 |
| `clutter-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:1.14.4-12.ael7b_1.1 |
| `clutter-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:1.14.4-12.ael7b_1.1 |
| `clutter-doc` | Red Hat:enterprise_linux:7::server | All versions | 0:1.14.4-12.ael7b_1.1 |
| `clutter` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.14.4-12.el7_1.1 |
| `clutter-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.14.4-12.el7_1.1 |
| `clutter-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.14.4-12.el7_1.1 |
| `clutter-doc` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.14.4-12.el7_1.1 |

Products: Clutter Project Clutter.

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

Upgrade to a fixed version.

## Is CVE-2015-3213 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-2190](https://insights.sbomify.com/CVE-2013-2190/): Denial of service in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-3213 is a high-severity authentication bypass vulnerability in n/a, published on 12 Aug 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-3213 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-2015-3213/ (Markdown: https://insights.sbomify.com/CVE-2015-3213/index.md)
```

## Sources

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

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