Front-Channel Parameter Handling in Okta Client SDK for Python
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Okta | Okta Client SDK for Python | unaffected |
|
No data.
No data.
No data available yet.
Vendor Solution
Upgrade the Okta Client SDK for Python to version 0.3.1 or greater. Customers should also rotate the client secret for any application that has run the authorization code flow without PAR.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The Okta Client SDK for Python (okta-client-python) includes client authentication values (client_secret or JWT assertions) as query parameters in the front-channel authorization URL when executing the authorization code flow without Pushed Authorization Requests (PAR). When PAR is disabled, unsupported by the authorization server, or fails, the SDK falls back to standard authorization URL construction, transmitting these parameters via user-agent requests. | |
| Title | Front-Channel Parameter Handling in Okta Client SDK for Python | |
| Weaknesses | CWE-522 CWE-598 |
|
| References |
| |
| Metrics |
cvssV3_1
|
No data.