API key disclosure via permissive registry access
Published Jun 30, 2022 · Updated Aug 3, 2024
Incorrect registry permissions in Ping Identity PingID for Windows login before 2.8 allow local users to read sensitive API keys. Under some circumstances, the integration stores its properties data under HKEY_LOCAL_MACHINE without restricting entry permissions to intended principals. A low-privileged local account is required, and exposed keys permit actions bounded by the API permissions assigned to the stored properties file.
Summary
What happened
Incorrect registry permissions in Ping Identity PingID for Windows login before 2.8 allow local users to read sensitive API keys. Under some circumstances, the integration stores its properties data under HKEY_LOCAL_MACHINE without restricting entry permissions to intended principals. A low-privileged local account is required, and exposed keys permit actions bounded by the API permissions assigned to the stored properties file.
The record
- CVE
- CVE-2022-23725
- Published
- Jun 30, 2022
- Updated
- Aug 3, 2024
- Vendor
- Ping Identity
- Product
- PingID for Windows login
- Classifications
- CWE-522, CWE-288, CWE-732, T1552.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 30, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <2.8
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