dbcve.org
PingfederateApplication · Pingidentity

CVE-2022-40722

MEDIUM · 5.8 CVSS v3.1 Published 2023-04-25
Fix available
A fix is available. Upgrade to 2.13.2 / 2.24 or later.
See remediation →
64/100
Remediation priority · Elevated
Remotely reachable 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
A misconfiguration of RSA padding implemented in the PingID Adapter for PingFederate to support Offline MFA with PingID mobile authenticators is vulnerable to pre-computed dictionary attacks, leading to a bypass of offline MFA.

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

The PingID Adapter for PingFederate has a misconfigured RSA padding implementation used for offline MFA with PingID mobile authenticators. This improper padding allows attackers to perform pre-computed dictionary attacks, enabling them to bypass the offline MFA protection mechanism.

MitigationConfigure proper RSA padding in the PingID Adapter for PingFederate according to vendor specifications, and verify that offline MFA functionality remains intact after the fix.

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
PingfederateApplication
Affected:>= 11.1.0, <= 11.1.5>= 11.2.0, <= 11.2.2
Pingid Adapter For PingfederateApplication
Affected:< 2.13.2
Pingid Integration KitApplication
Affected:< 2.24

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
Network
Complexity
High
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
None

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

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

  1. Check PingFederate version
    Locate the PingFederate installation and identify its version number (typically found in the admin console or version file)
    Affected if The version is 11.1.0 through 11.1.5, or 11.2.0 through 11.2.2
  2. Check PingID Adapter for PingFederate version
    Identify the installed version of the PingID Adapter for PingFederate component
    Affected if The version is earlier than 2.13.2
  3. Check PingID Integration Kit version
    Identify the installed version of the PingID Integration Kit
    Affected if The version is earlier than 2.24
  4. Verify offline MFA with PingID is enabled
    Inspect the PingFederate configuration to determine if offline MFA using PingID mobile authenticators is configured and active
    Affected if Offline MFA with PingID is enabled and any of the version conditions above are met

The environment is affected if offline MFA with PingID is active AND PingFederate is version 11.1.0-11.1.5/11.2.0-11.2.2, OR PingID Adapter is before 2.13.2, OR PingID Integration Kit is before 2.24.

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 2.13.2 / 2.24 or later
Fixed in 2.13.22.24
Interim mitigation

Configure proper RSA padding in the PingID Adapter for PingFederate according to vendor specifications, and verify that offline MFA functionality remains intact after the fix.

Recommended fix High confidence

PingFederate 11.1.6+ or 11.2.3+; PingID Adapter for PingFederate 2.13.2+; PingID Integration Kit 2.24+

  1. Back up your PingFederate configuration and database before upgrading.
  2. Download PingFederate version 11.1.6 or 11.2.3 (or later stable release) from the Ping Identity downloads portal.
  3. If using PingID Adapter for PingFederate, download version 2.13.2 or later.
  4. If using PingID Integration Kit, download version 2.24 or later.
  5. Follow the standard PingFederate upgrade procedure: stop the server, run the installer, and upgrade the configuration database.
  6. Restart the PingFederate service.
  7. Verify the upgrade by checking the admin console shows the new version and test offline MFA functionality to confirm the vulnerability is remediated.

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

Fix this in Pingfederate Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-40722 — 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-40722 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