Local PIN lockout bypass via attempt-limit evasion
Published Apr 25, 2023 · Updated Feb 4, 2025
Authentication bypass in Ping Identity PingID Desktop before 1.7.4 allows local users to evade the PIN-attempt lockout. The PIN-verification flow accepts attempts beyond the permitted maximum instead of activating the time-based lockout; Ping Identity has not disclosed the code-level locus. Local low-privilege access is required, and public materials establish defeat of the brute-force safeguard without specifying a further outcome.
Summary
What happened
Authentication bypass in Ping Identity PingID Desktop before 1.7.4 allows local users to evade the PIN-attempt lockout. The PIN-verification flow accepts attempts beyond the permitted maximum instead of activating the time-based lockout; Ping Identity has not disclosed the code-level locus. Local low-privilege access is required, and public materials establish defeat of the brute-force safeguard without specifying a further outcome.
The record
- CVE
- CVE-2022-40725
- Published
- Apr 25, 2023
- Updated
- Feb 4, 2025
- Vendor
- Ping Identity
- Product
- PingID Desktop
- Classifications
- CWE-306, CWE-288, T1110.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 25, 2023CVE publishedPublication date reported by the CVE source.
- Feb 4, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.7.4 <1.7.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
No public exploit references are available in this record.
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