keycloak: SAML broker does not check existence of signature on document allowing any user impersonation
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Red Hat | keycloak | affected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Runtimes Spring Boot 2.1.12 | |||
| keycloak | cpe:/a:redhat:openshift_application_runtimes:1.0 | RHSA-2020:2366 | 2020-06-04T00:00:00Z |
| Red Hat Single Sign-On 7.3.3 zip | |||
| keycloak | cpe:/a:redhat:jboss_single_sign_on:7.3 | RHSA-2019:2483 | 2019-08-13T00:00:00Z |
| Text-Only RHOAR | |||
| cpe:/a:redhat:openshift_application_runtimes:1.0 | RHSA-2020:2067 | 2020-05-18T00:00:00Z | |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2019-0650 | It was found that Keycloak's SAML broker, versions up to 6.0.1, did not verify missing message signatures. If an attacker modifies the SAML Response and removes the <Signature> sections, the message is still accepted, and the message can be modified. An attacker could use this flaw to impersonate other users and gain access to sensitive information. |
Github GHSA |
GHSA-4fgq-gq9g-3rw7 | Improper Verification of Cryptographic Signature in keycloak |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.714% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.