OpenAM OAuth Authorization Bypass via PKCE Challenge
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| OpenIdentityPlatform | OpenAM | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Openidentityplatform | Openam |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-4v2w-2wqp-mc85 | OpenAM OAuth Authorization Bypass via PKCE Challenge |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.529% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Openidentityplatform
Openidentityplatform openam |
|
| Vendors & Products |
Openidentityplatform
Openidentityplatform openam |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Open Access Management (OpenAM) is an access management solution. Prior to 16.1.1, AuthorizationCodeGrantTypeHandler requires a code_verifier only when the realm-wide codeVerifierEnforced setting is enabled, even when an authorization code stores a code_challenge. Because that setting is disabled by default, an attacker who intercepts a PKCE-protected authorization code can omit code_verifier and redeem the code, while an explicitly incorrect verifier is rejected. Public clients are directly affected, and confidential-client exploitation additionally requires client authentication material or another redemption context. This issue is fixed in version 16.1.1. | |
| Title | OpenAM OAuth Authorization Bypass via PKCE Challenge | |
| Weaknesses | CWE-285 | |
| References |
| |
| Metrics |
cvssV4_0
|