# CVE-2023-39930: PingFederate PingID Radius PCV Authentication Bypass

> Attackers can bypass first-factor authentication in PingFederate PingID Radius PCV by sending maliciously crafted RADIUS requests.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Oct 2023
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4x43-fwgv-cq8j

## What is CVE-2023-39930?

CVE-2023-39930 is a high-severity authentication bypass vulnerability in PingID Radius PCV, published on 24 Oct 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A 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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2023-39930?

It affects 1 product.


Products: Pingidentity Pingid Radius Pcv.

## How do I fix CVE-2023-39930?

No fix has been published for CVE-2023-39930 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-39930 being exploited?

There is no known exploitation of CVE-2023-39930 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-39930 and fix it if it is affected.

What it is: CVE-2023-39930 is a high-severity authentication bypass vulnerability in PingID Radius PCV, published on 24 Oct 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-39930 in the wild and no public exploit code.

Affected product: PingID Radius PCV. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-39930/ (Markdown: https://insights.sbomify.com/CVE-2023-39930/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-39930
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-39930
- OSV: https://osv.dev/vulnerability/CVE-2023-39930

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-39930/
Summaries are generated and may contain mistakes; the official description above is the record.