CVE-2023-40545: PingFederate OAuth client_secret_jwt Authentication Bypass
First published: Tue Feb 06 2024(Updated: )
Authentication bypass when an OAuth2 Client is using client_secret_jwt as its authentication method on affected 11.3 versions via specially crafted requests.
Credit: responsible-disclosure@pingidentity.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| PingFederate | =11.3.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2023-40545?
CVE-2023-40545 is classified as a critical severity vulnerability due to its potential for authentication bypass.
How do I fix CVE-2023-40545?
To fix CVE-2023-40545, update PingFederate to a version that is not affected by this vulnerability.
What versions of PingFederate are affected by CVE-2023-40545?
CVE-2023-40545 affects PingFederate version 11.3.0.
What type of vulnerability is CVE-2023-40545?
CVE-2023-40545 is an authentication bypass vulnerability when using the client_secret_jwt authentication method.
Who is at risk for CVE-2023-40545?
Organizations using PingFederate version 11.3.0 with OAuth2 client_secret_jwt for authentication are at risk for CVE-2023-40545.
- agent/weakness
- agent/title
- agent/references
- agent/type
- agent/description
- agent/first-publish-date
- agent/author
- agent/severity
- agent/softwarecombine
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/pingidentity
- canonical/pingfederate
- version/pingfederate/11.3.0