# CVE-2014-3202: Unity before 7.2.1 does not properly handle entry activation, which allows physically proximate attackers to bypass the lock screen by holdi


- **Severity:** Medium 4.4 (`AV:L/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 6 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-g93h-xxm7-w7m7, UBUNTU-CVE-2014-3202

## What is CVE-2014-3202?

CVE-2014-3202 is a medium-severity vulnerability in n/a, published on 6 May 2014. 

### Official description

Unity before 7.2.1 does not properly handle entry activation, which allows physically proximate attackers to bypass the lock screen by holding the ENTER key, which triggers the process to crash.

Weakness: CWE-264

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

It affects 1 product.


Products: Ayatana Project Unity.

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

Upgrade to a fixed version.

## Is CVE-2014-3202 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-5195](https://insights.sbomify.com/CVE-2014-5195/): Race condition in n/a (high 7.2)
- [CVE-2014-3203](https://insights.sbomify.com/CVE-2014-3203/): Auth bypass in n/a (medium 4.4)
- [CVE-2014-3204](https://insights.sbomify.com/CVE-2014-3204/): Auth bypass in n/a (medium 4.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-3202 is a medium-severity vulnerability in n/a, published on 6 May 2014. 
Exploitation: There is no known exploitation of CVE-2014-3202 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-3202/ (Markdown: https://insights.sbomify.com/CVE-2014-3202/index.md)
```

## Sources

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

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