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 by the authorization servers HTTP response to a request_uri authorization request, possibly leading to an information disclosure vulnerability.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat Build of Keycloak | RedHat | keycloak-core | * |
| Red Hat Build of Keycloak | RedHat | keycloak-core | * |
| Red Hat build of Keycloak 22 | RedHat | rhbk/keycloak-operator-bundle:22.0.11-2 | * |
| Red Hat build of Keycloak 22 | RedHat | rhbk/keycloak-rhel9:22-15 | * |
| Red Hat build of Keycloak 22 | RedHat | rhbk/keycloak-rhel9-operator:22-18 | * |
| Red Hat build of Keycloak 24 | RedHat | rhbk/keycloak-operator-bundle:24.0.5-2 | * |
| Red Hat build of Keycloak 24 | RedHat | rhbk/keycloak-rhel9:24-10 | * |
| Red Hat build of Keycloak 24 | RedHat | rhbk/keycloak-rhel9-operator:24-10 | * |
| Red Hat Single Sign-On 7 | RedHat | keycloak-core | * |
| Red Hat Single Sign-On 7.6 for RHEL 7 | RedHat | rh-sso7-keycloak-0:18.0.14-1.redhat_00001.1.el7sso | * |
| Red Hat Single Sign-On 7.6 for RHEL 8 | RedHat | rh-sso7-keycloak-0:18.0.14-1.redhat_00001.1.el8sso | * |
| Red Hat Single Sign-On 7.6 for RHEL 9 | RedHat | rh-sso7-keycloak-0:18.0.14-1.redhat_00001.1.el9sso | * |
| RHEL-8 based Middleware Containers | RedHat | rh-sso-7/sso76-openshift-rhel8:7.6-49 | * |
There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:
Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:
Information exposures can occur in different ways:
It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.