CVE-2022-23717
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 is vulnerable to a denial of service condition on local machines when combined with using offline security keys as part of authentication.
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 · moderate confidencePingID Windows Login versions prior to 2.8 contain a denial of service vulnerability that can be triggered on local Windows machines when users authenticate using offline security keys. The specific mechanism of the DoS condition is not detailed in available sources.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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 on the local system. Common locations include Program Files or the Windows registry under HKLM\SOFTWARE\PingIdentity or HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall. Look for entries named 'PingID' or 'PingID Windows Login' in installed programs.Affected if PingID Windows Login software is found on the system
-
Locate the installed versionFind the version number of the PingID Windows Login installation. Check the program's About dialog, the registry key containing the installed version, or examine the main executable file properties (right-click the PingID executable > Properties > Details). The version is typically displayed as a three-part number (e.g., 2.7.1).Affected if Unable to determine the version number from the installation
-
Compare version to affected rangeCompare your installed version against the affected range: versions prior to 2.8. If the version is 2.7.x, 2.6.x, or any version starting with 2.0 through 2.7, the system is in the affected range. Version 2.8 and later are not affected.Affected if Installed version is less than 2.8 (e.g., 2.7.0, 2.6.1, etc.)
-
Verify offline security key authentication is configuredCheck whether the PingID Windows Login configuration includes support for offline security key authentication. This is typically configured in the PingID admin console or local configuration settings. Look for FIDO2/WebAuthn or security key settings.Affected if Offline security key authentication is enabled and the version is below 2.8
The system is affected if PingID Windows Login is installed with a version lower than 2.8 and offline security key authentication is in use.
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 to remediate this vulnerability.
2.8 or later
- Download PingID Windows Login version 2.8 or later from the official PingIdentity download portal
- Install the updated PingID Windows Login package on all affected machines
- Restart the Windows Login service if required after installation
- Verify that offline security key authentication functions without causing denial of service conditions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23717 — 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-23717 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