CVE-2023-39930
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 · uneditedA first-factor authentication bypass vulnerability exists in the PingFederate with PingID Radius PCV when a MSCHAP authentication request is sent via a maliciously crafted RADIUS client request.
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 confidenceA critical first-factor authentication bypass vulnerability in PingFederate with PingID RADIUS PCV allows attackers to circumvent authentication controls by sending maliciously crafted MSCHAP authentication requests through a RADIUS client. This enables unauthorized access without valid credentials.
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>= 3.0.0, < 3.0.3CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify PingID RADIUS PCV installationLocate and query the PingID RADIUS PCV installation directory or use the product's built-in version command if availableAffected if The product is not installed or cannot be found (not affected)
-
Determine installed versionRetrieve the installed version of Pingidentity Pingid Radius Pcv and compare it to the affected range: 3.0.0 through 3.2.xAffected if Installed version is 3.0.0, 3.0.1, or 3.0.2 (or any version >= 3.0.0 but < 3.0.3)
-
Verify RADIUS client configuration existsInspect the PingFederate administrative console or configuration files for active RADIUS client definitionsAffected if No RADIUS clients are configured (not affected, as the attack requires a RADIUS client)
-
Confirm MSCHAP authentication is enabledReview the RADIUS client authentication policy settings to determine if MSCHAP or MSCHAPv2 authentication methods are permittedAffected if MSCHAP authentication is enabled - the vulnerability specifically exploits MSCHAP requests
You are affected if PingID RADIUS PCV version is 3.0.0-3.0.2 AND you have an active RADIUS client with MSCHAP authentication enabled.
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.
dbcve · scoped3.0.3
Immediately review and restrict RADIUS client configurations, disable MSCHAP authentication if not required, and apply the vendor patch when available. Implement additional monitoring on RADIUS authentication attempts.
PingID Radius PCV version 3.0.3 or later
- Obtain PingID Radius PCV version 3.0.3 or later from the Ping Identity download portal or your existing subscription
- Review the Ping Identity upgrade documentation for PingID Radius PCV
- Apply the upgrade following the standard upgrade procedure for your PingFederate deployment
- Verify the upgrade was successful by checking the version in the PingFederate admin console
- Test that MSCHAP authentication requests are now properly validated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39930 — 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-2023-39930 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