CVE-2013-4143: The (1) checkPasswd and (2) checkGroupXlockPasswds functions in xlockmore before 5.43 do not properly handle w

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

xlockmore: upgrade to newer than 5.42. Exact commands for each OS are on this page.

Q: Is CVE-2013-4143 being exploited?

CVE-2013-4143 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-4143 affect?

CVE-2013-4143 affects xlockmore. Severity is low (CVSS 2.1). The (1) checkPasswd and (2) checkGroupXlockPasswds functions in xlockmore before 5.43 do not properly handle when a NULL value is returned upon an error by the crypt or dispcrypt function as implemented in glibc 2.17 and later, which allows

Q: How urgent is CVE-2013-4143?

Priority 16/100. No elevated risk signals yet.

Routine

LOW 2.1UPGRADE

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

The (1) checkPasswd and (2) checkGroupXlockPasswds functions in xlockmore before 5.43 do not properly handle when a NULL value is returned upon an error by the crypt or dispcrypt function as implemented in glibc 2.17 and later, which allows attackers to bypass the screen lock via vectors related to invalid salts.

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.4% (top 66%)
CISA exploited list	No
Published	2014-05-30
Last modified	2026-06-16

Publisher (CNA): Red Hat, Inc. · Vendor: david bagley

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

Am I affected?

Timeline

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

david bagley xlockmore UPGRADE

Affected: <= 5.42 · 5.24 · 5.25 · 5.26 · 5.27 · 5.28 · 5.29 · 5.30

Fixed in: newer than 5.42

Safe to downgrade to: no unaffected older release

1. Check installed version

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

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

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade xlockmore

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-4143?

xlockmore: upgrade to newer than 5.42. Exact commands for each OS are on this page.

Is CVE-2013-4143 being exploited?

CVE-2013-4143 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-4143 affect?

CVE-2013-4143 affects xlockmore. Severity is low (CVSS 2.1). The (1) checkPasswd and (2) checkGroupXlockPasswds functions in xlockmore before 5.43 do not properly handle when a NULL value is returned upon an error by the crypt or dispcrypt function as implemented in glibc 2.17 and later, which allows

How urgent is CVE-2013-4143?

Priority 16/100. No elevated risk signals yet.

Software pages

glibc vulnerabilities

Related CVEs

CVE-2012-4524 HIGH 7.5 UPGRADE MITIGATE xlockmore before 5.43 'dclock' security bypass vulnerability
CVE-2006-0062 CRITICAL 9.8 DOWNGRADE xlockmore 5.13 allows potential xlock bypass when FVWM switches to the same virtual desktop as a new Gaim wind
CVE-2006-0061 CRITICAL 9.8 DOWNGRADE xlockmore 5.13 and 5.22 segfaults when using libpam-opensc and returns the underlying xsession

References

← Back to latest CVEs