dbcve.org
DesktopApplication · Pingidentity

CVE-2022-40725

MEDIUM · 6.1 CVSS v3.1 Published 2023-04-25
Fix available
A fix is available. Upgrade to 1.7.4 or later.
See remediation →
63/100
Remediation priority · Elevated
Zero-click

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 · unedited
PingID Desktop prior to the latest released version 1.7.4 contains a vulnerability that can be exploited to bypass the maximum PIN attempts permitted before the time-based lockout is activated.

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 confidence

PingID Desktop versions prior to 1.7.4 contain a vulnerability that allows bypassing the maximum PIN attempts limit before the time-based lockout is triggered, potentially enabling brute-force attacks against user PINs.

MitigationUpgrade PingID Desktop to version 1.7.4 or later to obtain the patch for this vulnerability.

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
DesktopApplication
Affected:< 1.7.4

CVSS 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
Low
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed PingID Desktop version
    Check the installed version of PingID Desktop through system inventory, package manager, or application about/help menu
    Affected if Version is below 1.7.4
  2. Confirm PIN-based authentication is in use
    Verify whether PIN is enabled as an authentication factor in the PingID Desktop configuration
    Affected if PIN authentication is configured or in use
  3. Check PIN attempt lockout configuration
    Inspect the application settings or policy configuration to see the maximum PIN attempts allowed before lockout
    Affected if The limit can be bypassed before time-based lockout triggers

User is affected if PingID Desktop version is below 1.7.4 and PIN-based authentication is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.7.4 or later
Fixed in 1.7.4
Interim mitigation

Upgrade PingID Desktop to version 1.7.4 or later to obtain the patch for this vulnerability.

Recommended fix Moderate confidence

1.7.4

  1. Obtain PingID Desktop version 1.7.4 from the official Ping Identity download portal or your organization's software distribution system
  2. Uninstall the current version of PingID Desktop from the affected system
  3. Install PingID Desktop version 1.7.4
  4. Verify the installation by checking the application version in the PingID Desktop application settings or about menu
  5. Ensure the maximum PIN attempts configuration is properly set according to your organization's security policy

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Desktop Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-40725 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-40725 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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