dbcve.org
Pingone Mfa Integration KitApplication · Pingidentity

CVE-2023-39231

MEDIUM · 6.5 CVSS v3.1 Published 2023-10-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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
PingFederate using the PingOne MFA adapter allows a new MFA device to be paired without requiring second factor authentication from an existing registered device. A threat actor may be able to exploit this vulnerability to register their own MFA device if they have knowledge of a victim user's first factor credentials.

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 confidence

The PingOne MFA adapter in PingFederate fails to require second-factor verification from an already-registered device when pairing a new MFA device. An attacker who has obtained a victim's first-factor credentials (username/password) can register their own MFA device to the victim's account without proving access to an existing enrolled device, effectively bypassing the second authentication factor.

MitigationDisable or restrict new MFA device pairing in the PingOne MFA adapter configuration, or implement additional verification steps requiring existing device confirmation before allowing registration of new devices.

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:= 2.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
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Identify PingOne MFA Integration Kit version
    Locate the installed PingOne MFA Integration Kit installation directory and check the version file or manifest. Common locations include the PingFederate installation's directory under /hooks or /integrations. Run 'java -jar' against the adapter jar file with version flag, or check the kit's release notes if accessible.
    Affected if The installed version is exactly 2.2, indicating the vulnerable version of the integration kit.
  2. Verify PingOne MFA adapter is configured in PingFederate
    Access the PingFederate administrative console and navigate to the Authentication > Adapters section. Confirm that the PingOne MFA adapter instance is created and actively assigned to any authentication policies or applications.
    Affected if A PingOne MFA adapter instance exists and is in active use, meaning the vulnerable component is exposed.
  3. Check if new MFA device pairing is enabled
    In the PingOne MFA adapter configuration screen within PingFederate console, examine the adapter settings for options related to device enrollment, device pairing, or new device registration. Look for checkboxes or toggles controlling whether users can register additional authentication devices.
    Affected if The adapter configuration allows users to pair or register new MFA devices without requiring verification of an already-enrolled device.
  4. Review authentication policies using the adapter
    Navigate to Authentication > Policies in PingFederate and identify which authentication policies reference the PingOne MFA adapter. Determine if these policies are used for production or sensitive applications.
    Affected if The vulnerable adapter is part of authentication policies protecting user accounts, enabling the bypass attack path.

A user is affected if PingOne MFA Integration Kit version 2.2 is installed with a PingOne MFA adapter that permits new device pairing without existing device verification, and that adapter is active in authentication policies.

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

Disable or restrict new MFA device pairing in the PingOne MFA adapter configuration, or implement additional verification steps requiring existing device confirmation before allowing registration of new devices.

Fix this in Pingone Mfa Integration Kit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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