CVE-2012-1620: slock 0.9 does not properly handle the XRaiseWindow event when the screen is locked, which might allow physica

Routine

LOW 3.6DOWNGRADE

CVE-2012-1620 is a low-severity flaw (CVSS 3.6) affecting slock. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

slock 0.9 does not properly handle the XRaiseWindow event when the screen is locked, which might allow physically proximate attackers to obtain sensitive information by pressing a button, which reveals the desktop and active windows.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	3.6 (Low)
EPSS exploit chance	0.5% (top 57%)
CISA exploited list	No
Weakness	CWE-264
Published	2012-07-12
Last modified	2026-06-16

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

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

Am I affected?

Timeline

2012-07-12 19:55 UTCPublished CVE record published
2026-06-16 23:39 UTCUpdated Record last modified

suckless slock DOWNGRADE

Affected: 0.9

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.9

1. Check installed version

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

2. No fixed release: DOWNGRADE to a release before 0.9 (Debian / Ubuntu)

apt-cache madison slock sudo apt install slock=<VERSION_BEFORE_0.9> sudo apt-mark hold slock

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list slock sudo dnf downgrade slock-<VERSION_BEFORE_0.9> sudo dnf versionlock add slock

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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

slock: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2012-1620 being exploited?

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

CVE-2012-1620 affects slock. Severity is low (CVSS 3.6). slock 0.9 does not properly handle the XRaiseWindow event when the screen is locked, which might allow physically proximate attackers to obtain sensitive information by pressing a button, which reveals the desktop and active windows.

How urgent is CVE-2012-1620?

Priority 28/100. Public exploit reference

Software pages

Windows vulnerabilities

Related CVEs

CVE-2020-36455 HIGH 8.1 UPGRADE An issue was discovered in the slock crate through 2020-11-17 for Rust
CVE-2016-6866 HIGH 7.5 UPGRADE MITIGATE slock allows attackers to bypass the screen lock via vectors involving an invalid password hash, which trigger

References

← Back to latest CVEs