CVE-2022-40723
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 · uneditedThe PingID RADIUS PCV adapter for PingFederate, which supports RADIUS authentication with PingID MFA, is vulnerable to MFA bypass under certain configurations.
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 confidenceThe PingID RADIUS PCV adapter for PingFederate contains a vulnerability that allows MFA bypass under certain configuration conditions. An attacker with valid primary credentials could potentially bypass PingID MFA enforcement and authenticate solely via RADIUS without completing multi-factor authentication.
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>= 11.1.0, <= 11.1.5>= 11.2.0, <= 11.2.2< 2.24>= 3.0.0, < 3.0.2= 2.10.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify PingFederate versionLocate the PingFederate installation directory and check the version file (typically in <pf_install>/pingfederate/lib or via admin console). Compare the installed version against the affected ranges: 11.1.0-11.1.5 or 11.2.0-11.2.2.Affected if The installed PingFederate version falls within 11.1.0-11.1.5 or 11.2.0-11.2.2.
-
Identify PingID Integration Kit versionLocate the PingID Integration Kit (usually in <pf_install>/pingfederate/lib or observed in the PingFederate admin console under "Installed Plugins"). Check the version number.Affected if The installed PingID Integration Kit version is below 2.24.
-
Identify RADIUS PCV adapter versionIn PingFederate admin console, navigate to "Adapters" and locate the RADIUS PCV adapter instance. Check its version, or inspect the adapter JAR file in the installation lib directory.Affected if The RADIUS PCV adapter version is 2.10.0, or between 3.0.0 and 3.0.1 (less than 3.0.2).
-
Confirm RADIUS PCV adapter is in useIn PingFederate admin console, check "Adapters" to see if a RADIUS PCV adapter instance exists and is configured for any authentication policies or applications.Affected if A RADIUS PCV adapter is deployed and active in the PingFederate environment.
-
Verify PingID MFA enforcement on RADIUS adapterIn PingFederate admin console, open the RADIUS PCV adapter configuration. Inspect the MFA enforcement settings, specifically looking for whether PingID MFA is properly enforced or if there are conditions that could allow bypass (such as "fail open" or weak policy rules).Affected if The adapter is configured but PingID MFA enforcement is missing, weak, or misconfigured.
The environment is affected if PingFederate (11.1.0-11.1.5 or 11.2.0-11.2.2) is running with a vulnerable RADIUS PCV adapter (2.10.0 or 3.0.0-3.0.1) and PingID Integration Kit below 2.24, where the adapter is active and MFA enforcement may be improperly applied.
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.
From vendor data2.243.0.2
Review and harden the PingID RADIUS PCV adapter configuration settings in PingFederate to ensure MFA enforcement is properly applied. Apply any available vendor patches or updates to the adapter.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40723 — 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-40723 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