# CVE-2013-4427: Security feature bypass in n/a

> A local attacker can bypass the screen lock in pyxtrlock by exploiting unchecked return values in XCB functions, gaining unauthorized keyboard and mouse access.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-ghjf-v3fm-fh8c

## What is CVE-2013-4427?

CVE-2013-4427 is a low-severity vulnerability in n/a, published on 19 May 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

pyxtrlock before 0.2 does not properly check the return values of the (1) xcb_grab_pointer and (2) xcb_grab_keyboard XCB library functions, which allows physically proximate attackers to gain access to the keyboard or mouse without unlocking the screen via unspecified vectors.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2013-4427?

It affects 1 product.


Products: Leon Weber Pyxtrlock.

## How do I fix CVE-2013-4427?

No fix has been published for CVE-2013-4427 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-4427 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-4426](https://insights.sbomify.com/CVE-2013-4426/): Auth bypass in n/a (low 3.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4427 and fix it if it is affected.

What it is: CVE-2013-4427 is a low-severity vulnerability in n/a, published on 19 May 2014. 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 CVE-2013-4427 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-2013-4427/ (Markdown: https://insights.sbomify.com/CVE-2013-4427/index.md)
```

## Sources

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

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