CVE-2012-4524: xlockmore before 5.43 'dclock' security bypass vulnerability

Q: How do I fix CVE-2012-4524?

xlockmore: upgrade to 5.43; fedora: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2012-4524 being exploited?

CVE-2012-4524 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-2012-4524 affect?

CVE-2012-4524 affects xlockmore, fedora. Severity is high (CVSS 7.5). xlockmore before 5.43 'dclock' security bypass vulnerability

Q: How urgent is CVE-2012-4524?

Priority 53/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADEMITIGATE

CVE-2012-4524 is a high-severity flaw (CVSS 7.5) affecting xlockmore, fedora. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

xlockmore before 5.43 'dclock' security bypass vulnerability

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.9% (top 13%)
CISA exploited list	No
Weakness	CWE-20
Published	2019-11-21
Last modified	2026-06-16

Publisher (CNA): Red Hat, Inc. · Vendor: fedoraproject · sillycycle

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

Am I affected?

Timeline

2019-11-21 15:15 UTCPublished CVE record published
2026-06-16 23:45 UTCUpdated Record last modified

sillycycle xlockmore UPGRADE

Affected: < 5.43

Fixed in: 5.43

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 5.43 (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.

fedoraproject fedora MITIGATE

Affected: 16 · 17 · 18

Fixed in: no fixed release known

Safe to downgrade to: a release before 16

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

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-2012-4524?

xlockmore: upgrade to 5.43; fedora: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2012-4524 being exploited?

CVE-2012-4524 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-2012-4524 affect?

CVE-2012-4524 affects xlockmore, fedora. Severity is high (CVSS 7.5). xlockmore before 5.43 'dclock' security bypass vulnerability

How urgent is CVE-2012-4524?

Priority 53/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

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