dbcve.org
Pingone Mfa Integration KitApplication · Pingidentity

CVE-2022-23723

HIGH · 7.7 CVSS v3.1 Published 2022-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
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
An MFA bypass vulnerability exists in the PingFederate PingOne MFA Integration Kit when adapter HTML templates are used as part of an authentication flow.

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

An MFA bypass vulnerability exists in PingFederate's PingOne MFA Integration Kit where authentication flows utilizing adapter HTML templates can circumvent multi-factor authentication requirements, allowing attackers to potentially gain unauthorized access without completing MFA verification.

MitigationReview and remediate authentication policies in PingFederate that use adapter HTML templates with PingOne MFA Integration Kit to ensure MFA challenges are properly enforced; consider updating to patched versions of the integration kit and validating that all authentication flows correctly require MFA completion.

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
Pingone Mfa Integration KitApplication
Affected:= 1.4= 1.4.1= 1.5= 1.5.1= 1.5.2

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

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

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

  1. Identify PingOne MFA Integration Kit installation and version
    Locate the PingOne MFA Integration Kit installation directory and check the version file or manifest. Common locations include the PingFederate deploy directory or the kit's own installation folder. Compare the installed version against the affected list: 1.4, 1.4.1, 1.5, 1.5.1, 1.5.2.
    Affected if The installed version matches one of the affected versions listed in the CVE.
  2. Determine if adapter HTML templates are in use
    Review the PingFederate authentication configuration to identify whether any adapter HTML templates are configured. Check the authentication policy definitions and adapter instances for custom HTML template references.
    Affected if Adapter HTML templates are configured and used within authentication flows alongside the PingOne MFA Integration Kit.
  3. Identify authentication flows using the vulnerable configuration
    Examine authentication policies and flows in PingFederate that combine PingOne MFA Integration Kit with adapter-based HTML templates. Review the policy tree to identify which flows include both components.
    Affected if Authentication policies exist that use adapter HTML templates together with the PingOne MFA Integration Kit for MFA processing.
  4. Verify MFA enforcement in affected authentication policies
    Review the specific MFA adapter configuration within those authentication flows. Check whether the MFA challenge is properly enforced before authentication completion, or if the flow can complete without successful MFA verification.
    Affected if The authentication flow using adapter HTML templates with PingOne MFA can complete without requiring successful MFA verification.

You are affected if PingOne MFA Integration Kit versions 1.4 through 1.5.2 are installed and authentication policies use adapter HTML templates in combination with the MFA integration kit, allowing flows to potentially bypass MFA verification.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Review and remediate authentication policies in PingFederate that use adapter HTML templates with PingOne MFA Integration Kit to ensure MFA challenges are properly enforced; consider updating to patched versions of the integration kit and validating that all authentication flows correctly require MFA completion.

Fix this in Pingone Mfa Integration Kit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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