# CVE-2012-0064: Security feature bypass in n/a

> Physically proximate attackers can bypass X screen locks using keyboard combinations due to default debugging functions in xkeyboard-config.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-0064, GHSA-h73q-jx23-45rq

## What is CVE-2012-0064?

CVE-2012-0064 is a medium-severity vulnerability in n/a, published on 10 Feb 2014. 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

xkeyboard-config before 2.5 in X.Org before 7.6 enables certain XKB debugging functions by default, which allows physically proximate attackers to bypass an X screen lock via keyboard combinations that break the input grab.

Weakness: CWE-264

## Which versions are affected by CVE-2012-0064?

It affects 2 products.


Products: X X.org X11, Xkeyboard Config Project Xkeyboard-Config.

## How do I fix CVE-2012-0064?

Upgrade to a fixed version.

## Is CVE-2012-0064 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-4396](https://insights.sbomify.com/CVE-2013-4396/): Use after free in n/a (medium 6.5)
- [CVE-2012-1699](https://insights.sbomify.com/CVE-2012-1699/): Memory corruption in n/a (low 3.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-0064 and fix it if it is affected.

What it is: CVE-2012-0064 is a medium-severity vulnerability in n/a, published on 10 Feb 2014. 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-2012-0064 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-2012-0064/ (Markdown: https://insights.sbomify.com/CVE-2012-0064/index.md)
```

## Sources

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

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