CVE-2022-23725
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPingID Windows Login prior to 2.8 does not properly set permissions on the Windows Registry entries used to store sensitive API keys under some circumstances.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencePingID Windows Login versions prior to 2.8 fail to set proper access control permissions on Windows Registry keys that store sensitive API keys, potentially allowing lower-privileged users or malicious actors to read these credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.8CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify PingID Windows Login is installedCheck for PingID Windows Login installation by reviewing installed programs in Windows Settings > Apps & Features, or query the Windows Installer database using: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*PingID*'}.Affected if PingID Windows Login is present on the system.
-
Determine installed versionLocate the installed version of PingID Windows Login. This can typically be found in the program properties (right-click the application in Programs and Features, or check the version field), or by examining the executable version information if located in the installation directory.Affected if The installed version is less than 2.8 (e.g., 2.7, 2.6, etc.).
-
Identify registry keys storing API keysExamine the Windows Registry for keys related to PingID that may contain sensitive API credentials. These are typically found under HKEY_LOCAL_MACHINE\SOFTWARE\Ping Identity or HKEY_CURRENT_USER\SOFTWARE\Ping Identity. Use Registry Editor (regedit) or PowerShell to locate and list keys under these paths.Affected if Registry keys containing PingID API keys or credentials exist on the system.
-
Inspect registry key access control permissionsRight-click on each identified PingID registry key in Registry Editor, select Permissions, and review the entries in the Security tab. Alternatively, use PowerShell: Get-Acl -Path 'HKLM:\SOFTWARE\Ping Identity\*' | Select-Object PSPath, AccessToString to view who has read or full control access.Affected if Users with lower privileges (non-administrators) or the 'Users' group have been granted Read or Full Control permissions to registry keys containing API keys, allowing unauthorized access to credentials.
The system is affected if PingID Windows Login version prior to 2.8 is installed AND registry keys storing API keys are readable by lower-privileged users due to improper access control permissions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.8
Upgrade PingID Windows Login to version 2.8 or later which properly secures registry entries; audit affected systems for unauthorized access to API keys.
PingID Windows Login 2.8
- Verify the current installed version of PingID Windows Login
- Download PingID Windows Login version 2.8 or later from the official PingIdentity download portal
- Follow the standard PingID Windows Login upgrade documentation for your deployment model
- After upgrade, verify that registry permissions are properly set on the sensitive API key entries
- Test PingID Windows Login authentication functionality to confirm the upgrade was successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23725 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-23725 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data