Keycloak exposes sensitive information in Pushed Authorization Requests (PAR)
A flaw was found in Keycloak in the OAuth 2.0 Pushed Authorization Requests (PAR). Client provided parameters were found to be included in plain text in the KC_RESTART cookie returned by the authorization server's HTTP response to a request_uri authorization request. This could lead to an information disclosure vulnerability.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2024-4540US | —OT elevated | — | ||
A flaw was found in Keycloak in OAuth 2.0 Pushed Authorization Requests (PAR). Client-provided parameters were found to be included in plain text in the KC_RESTART cookie returned… | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2024:3566WEB
- https://access.redhat.com/errata/RHSA-2024:3567WEB
- https://access.redhat.com/errata/RHSA-2024:3568WEB
- https://access.redhat.com/errata/RHSA-2024:3570WEB
- https://access.redhat.com/errata/RHSA-2024:3572WEB
- https://access.redhat.com/errata/RHSA-2024:3573WEB
- https://access.redhat.com/errata/RHSA-2024:3574WEB
- https://access.redhat.com/errata/RHSA-2024:3575WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan