Local lockscreen bypass via writable configuration hash
Published Feb 5, 2021 · Updated Aug 4, 2024
Lockscreen bypass in Psyprax before 3.2.2 allows local users to disable the application lock through a writable configuration file. The PPScreen.ini file under C:\ProgramData\Psyprax32 stores the lockscreen hash, but its permissions allow every local user to delete that entry, after which Psyprax does not display the lockscreen or lock the application. An attacker requires a local Windows account and file access; successful exploitation removes the application access barrier without changing the Windows session lock.
Summary
What happened
Lockscreen bypass in Psyprax before 3.2.2 allows local users to disable the application lock through a writable configuration file. The PPScreen.ini file under C:\ProgramData\Psyprax32 stores the lockscreen hash, but its permissions allow every local user to delete that entry, after which Psyprax does not display the lockscreen or lock the application. An attacker requires a local Windows account and file access; successful exploitation removes the application access barrier without changing the Windows session lock.
The record
- CVE
- CVE-2020-10553
- Published
- Feb 5, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-522, CWE-732, T1562.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 5, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Screensaver Password not protected reproduction procedureproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo