CVE-2013-4427: pyxtrlock before 0.2 does not properly check the return values of the (1) xcb_grab_pointer and (2) xcb_grab_ke

Q: How do I fix CVE-2013-4427?

pyxtrlock: upgrade to newer than 0.1. Exact commands for each OS are on this page.

Q: Is CVE-2013-4427 being exploited?

CVE-2013-4427 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2013-4427 affect?

CVE-2013-4427 affects pyxtrlock. Severity is low (CVSS 2.1). 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 unlockin

Q: How urgent is CVE-2013-4427?

Priority 14/100. No elevated risk signals yet.

Routine

LOW 2.1UPGRADE

CVE-2013-4427 is a low-severity flaw (CVSS 2.1) affecting pyxtrlock. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	2.1 (Low)
EPSS exploit chance	0.3% (top 72%)
CISA exploited list	No
Weakness	CWE-20
Published	2014-05-19
Last modified	2026-06-16

Publisher (CNA): Red Hat, Inc. · Vendor: leon weber

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2014-05-19 14:55 UTCPublished CVE record published
2026-06-16 23:57 UTCUpdated Record last modified

leon weber pyxtrlock UPGRADE

Affected: <= 0.1 · 0.1 beta

Fixed in: newer than 0.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy pyxtrlock || rpm -q pyxtrlock || pyxtrlock --version

2. UPGRADE to newer than 0.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade pyxtrlock

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade pyxtrlock

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2013-4427?

pyxtrlock: upgrade to newer than 0.1. Exact commands for each OS are on this page.

Is CVE-2013-4427 being exploited?

CVE-2013-4427 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2013-4427 affect?

CVE-2013-4427 affects pyxtrlock. Severity is low (CVSS 2.1). 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 unlockin

How urgent is CVE-2013-4427?

Priority 14/100. No elevated risk signals yet.

Related CVEs

CVE-2019-1010316 HIGH 7.8 UPGRADE pyxtrlock 0.3 and earlier is affected by: Incorrect Access Control
CVE-2013-4426 LOW 3.6 UPGRADE pyxtrlock before 0.1 uses an incorrect variable name, which allows physically proximate attackers to bypass th

References

← Back to latest CVEs