CVE-2023-6134
CVE-2023-6134: 2 tracked advisory records across Red Hat. Compare vendor sources and published fix guidance.
Compare the source-linked records below. Ratings and product/version details belong to each advisory; they are not a single CVE-wide score or proof that every listed product is affected. How VulniPulse collects and checks evidence.
Vendor advisory comparison
Red Hat
2 advisories- Advisory severityMedium4.6
Medium [CVE-2023-6134 +1] Keycloak: open redirect via "form_post.jwt" jarm response mode
CVE-2023-6927Source published Source updated
This bulletin covers 2 CVEs. The products, versions, score and guidance below describe the bulletin; check its source for applicability to this specific CVE.
A flaw was found in Keycloak. This issue may allow an attacker to steal authorization codes or tokens from clients using a wildcard in the JARM response mode "form_post.jwt" which could be used to bypass the security patch implemented to address CVE-2023-6134. Red Hat rates this as a moderate, following the same case for CVE-2023-6134, but with another response mode with JSON Web Token. Red Hat severity: Moderate — CVSS 4.6 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N). Weakness: CWE-601. Affected Red Hat products: Red Hat build of Keycloak 22; Red Hat build of Keycloak 22.0.8; Red Hat Single Sign-On 7; Red Hat Single Sign-On 7.6 for RHEL 7; Red Hat Single Sign-On 7.6 for RHEL 8; Red Hat Single Sign-On 7.6 for RHEL 9; RHEL-8 based Middleware Containers; Single Sign-On 7.6.6. Red Hat…
- Affected products in this advisory
- Red Hat build of Keycloak 22.0.8
- Red Hat Single Sign-On 7.6 for RHEL 7
- Red Hat Single Sign-On 7.6 for RHEL 8
- Red Hat Single Sign-On 7.6 for RHEL 9
2 more entries in the full advisory.
- Source-reported affected versions
- Affected-version details not available in this record.
- Source-reported fixed versions
- rhbk/keycloak-rhel9:22-7
- keycloak-core
- rh-sso7-keycloak
- rh-sso7-keycloak-0:18.0.11-3.redhat_00001.1.el7sso
19 more entries in the full advisory.
- Mitigation guidance
- Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
- Advisory severityMedium4.6
Medium [CVE-2020-10748 +1] Keycloak: reflected xss via wildcard in oidc redirect_uri
CVE-2023-6134Source published Source updated
This bulletin covers 2 CVEs. The products, versions, score and guidance below describe the bulletin; check its source for applicability to this specific CVE.
A flaw was found in Keycloak that prevents certain schemes in redirects, but permits them if a wildcard is appended to the token. This issue could allow an attacker to submit a specially crafted request leading to cross-site scripting (XSS) or further attacks. This flaw is the result of an incomplete fix for CVE-2020-10748. Red Hat severity: Moderate — CVSS 4.6 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N). Weakness: CWE-79. Affected Red Hat products: Red Hat build of Keycloak 22; Red Hat build of Keycloak 22.0.7; Red Hat Single Sign-On 7; Red Hat Single Sign-On 7.6 for RHEL 7; Red Hat Single Sign-On 7.6 for RHEL 8; Red Hat Single Sign-On 7.6 for RHEL 9; RHEL-8 based Middleware Containers; Single Sign-On 7.6.6. Red Hat fixing advisory: RHSA-2023:7861, RHSA-2023:7860, RHSA-2024:0804…
- Affected products in this advisory
- Red Hat build of Keycloak 22.0.7
- Red Hat Single Sign-On 7.6 for RHEL 7
- Red Hat Single Sign-On 7.6 for RHEL 8
- Red Hat Single Sign-On 7.6 for RHEL 9
2 more entries in the full advisory.
- Source-reported affected versions
- Affected-version details not available in this record.
- Source-reported fixed versions
- rhbk/keycloak-operator-bundle:22.0.7-1
- rhbk/keycloak-rhel9:22-6
- rhbk/keycloak-rhel9-operator:22-9
- rh-sso7-keycloak
21 more entries in the full advisory.
- Mitigation guidance
- No mitigation guidance extracted; consult the source.
Android app · Google Play
Monitor future Red Hat CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.