OAuth client authentication bypass via crafted requests
Published Feb 6, 2024 · Updated Aug 22, 2024
Authentication bypass in Ping Identity PingFederate 11.3.0 through 11.3.2 allows remote authenticated users to bypass OAuth client authentication. Public sources identify crafted requests for clients configured with client_secret_jwt but do not disclose the faulty validation operation. A configured OAuth client and network access to an applicable OAuth endpoint are required, and successful bypass compromises that client's protected OAuth operations.
Summary
What happened
Authentication bypass in Ping Identity PingFederate 11.3.0 through 11.3.2 allows remote authenticated users to bypass OAuth client authentication. Public sources identify crafted requests for clients configured with client_secret_jwt but do not disclose the faulty validation operation. A configured OAuth client and network access to an applicable OAuth endpoint are required, and successful bypass compromises that client's protected OAuth operations.
The record
- CVE
- CVE-2023-40545
- Published
- Feb 6, 2024
- Updated
- Aug 22, 2024
- Vendor
- Ping Identity
- Product
- PingFederate
- Classifications
- CWE-306, CAPEC-115, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 6, 2024CVE publishedPublication date reported by the CVE source.
- Aug 22, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=11.3.0 <=11.3.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo