Build Of Keycloak vulnerabilities
36 known vulnerabilities in Build Of Keycloak from Red Hat. 36 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 8.1 High severity
Red Hat Build of Keycloak: Authentication Bypass by Capture-replay
A flaw was found in the SAML broker component of Keycloak, an identity and access management solution. When configured as a SAML broker using the IdP-Initiated flow, Keycloak fails to enforce the OneTimeUse condition in SAML assertions. This allows an attacker
- 9.8 Critical severity
Red Hat build of Keycloak 26.4: Origin Validation Error
A flaw was found in the SAML broker component of Keycloak, which is used to manage identity federation and user authentication. The issue occurs because the IdP-initiated Single Sign-On endpoint fails to check if a provider is restricted to account linking onl
- 8.8 High severity
Red Hat build of Keycloak 26.4: Access of Resource Using Incompatible Type
A flaw was found in Keycloak's Dynamic Client Registration (DCR) security policy management. The "Allowed Protocol Mapper Types" policy, which restricts which types of data mappers a client can use, fails to re-validate the mapper type during a client update i
- 8.1 High severity
Red Hat build of Keycloak 26.4: Incorrect Behavior Order: Authorization Before Parsing and Canonicalization
A flaw was found in the Dynamic Client Registration (DCR) component of Keycloak, an identity and access management solution. The default DCR policy fails to properly validate the claim path for User Property mappers, allowing them to write values to sensitive
- 8.1 High severity
Red Hat build of Keycloak 26.4: Incorrect Behavior Order: Authorization Before Parsing and Canonicalization
A flaw was found in Keycloak's Authorization Services. The component responsible for matching request paths to security policies (PathMatcher) does not properly normalize URIs before comparison. By adding extra characters like a trailing slash or matrix parame
- 9.1 Critical severity
Red Hat build of Keycloak 26.4: Improper Verification of Cryptographic Signature
A flaw was found in the SAML metadata import functionality of the keycloak-services component, which is the core engine for identity brokering in Red Hat Build of Keycloak. When importing identity provider metadata that lacks specific usage attributes for keys
- 7.2 High severity
Red Hat build of Keycloak 26.6: Missing Authorization
A flaw was found in the user creation component of Keycloak when Fine-Grained Admin Permissions V2 (FGAP V2) is enabled. This issue allows a sub-administrator with permission to create users to add those users to any group, even groups the sub-administrator is
- 8.1 High severity
Red Hat build of Keycloak 26.6: Improper Authentication
Keycloak provides a way to let users log in using Microsoft accounts while restricting access to a specific organization (tenant). A flaw was discovered where this restriction is ignored when using the token exchange feature. This means an attacker with a vali
- 8.1 High severity
Red Hat build of Keycloak 26.6: Missing Authorization
Keycloak allows users to log in using Google accounts and can be configured to only allow users from specific Google Workspace domains. A flaw was found where the token exchange feature, which allows swapping a Google token for a Keycloak token, does not check
- 8.1 High severity
Keycloak: Improper Access Control
A flaw was found in Keycloak. When the JSON Web Token (JWT) authorization grant preview feature is enabled and a user account is disabled, Keycloak fails to validate the user’s disabled status during JWT authorization grant processing. A remote attacker with l
- 8.1 High severity
Red Hat build of Keycloak 26.6: Improper Verification of Cryptographic Signature
A flaw was found in Keycloak. This JWT algorithm confusion vulnerability in the JWT Authorization Grant flow allows an attacker with valid client credentials to bypass signature verification. By forging an assertion, the attacker can create unauthorized access
- 8.1 High severity
Red Hat build of Keycloak 26.4: Comparison Using Wrong Factors
A flaw was found in Keycloak Policy Enforcer. This vulnerability allows any authenticated user to bypass all authorization policies, including role, scope, and User-Managed Access (UMA) permission checks. By including the configured access-denied page path wit
- 7.7 High severity
Red Hat build of Keycloak 26.4: Authorization Bypass Through User-Controlled Key
A flaw was found in Keycloak. A missing authorization check in the GroupResource.addChild() endpoint within the Admin REST API allows an authenticated user with limited administrative privileges to reparent any existing group. When Fine-Grained Admin Permissio
- 7.3 High severity
Red Hat build of Keycloak 26.4: Improper Neutralization of Input During Web Page Generation
A flaw was found in Keycloak. A remote attacker with administrative privileges, specifically those with `manage-client` permission or access to client registration endpoints, could bypass client Uniform Resource Identifier (URI) validation. This is achieved by
- 7.3 High severity
Red Hat build of Keycloak 26.4: Incorrect Privilege Assignment
A flaw was found in Keycloak's Fine-Grained Admin Permissions (FGAPv2) feature. An administrator with limited client management permissions can exploit this vulnerability to assign any realm role, including highly privileged roles, to a client's scope mapping.
- 7.5 High severity
Red Hat build of Keycloak 26.4: Improper Verification of Cryptographic Signature
A flaw was found in Keycloak. When a JSON Web Encryption (JWE) encrypted request object is submitted, Keycloak may incorrectly process unsigned claims if the decrypted content is raw JSON, bypassing the configured signature policy. This allows a remote attacke
- 8.8 High severity
Red Hat build of Keycloak 26.4: Improper Validation of Specified Quantity in Input
A flaw was found in Keycloak. An authenticated user with low privileges can exploit this vulnerability by sending an oversized subject_token JSON Web Token (JWT) to the TokenEndpoint. When the token exceeds a 4000-character limit, it is silently dropped, causi
- 8.1 High severity
Red Hat build of Keycloak 26.4: Authorization Bypass Through User-Controlled Key
A flaw was found in Keycloak. The cross-session verification proof is keyed only by (local userId, idpAlias) and is not bound to the upstream identity that was actually verified, so a second upstream account on the same IdP can consume it and get linked to the
- 7.1 High severity
Red Hat build of Keycloak 26.4: External Control of Assumed-Immutable Web Parameter
A flaw was found in Keycloak. A low-privilege user, with knowledge of user credentials and client ID, can bypass a security control intended to disable the implicit flow in OpenID Connect (OIDC) clients. By manipulating client data during a session restart, an
- 7.5 High severity
Red Hat build of Keycloak 26.2: Authentication Bypass by Spoofing
A session fixation vulnerability was found in Keycloak's login-actions endpoints. An unauthenticated attacker could exploit this flaw by pre-creating an authentication session and tricking a victim into visiting a maliciously crafted link. By leveraging the /l
- 8.1 High severity
Red Hat build of Keycloak 26.2: URL Redirection to Untrusted Site
A flaw was found in Keycloak's URL validation logic during redirect operations. By crafting a malicious request, an attacker could bypass validation to redirect users to unauthorized URLs, potentially leading to the exposure of sensitive information within the
- 7.5 High severity
Red Hat build of Keycloak 26.2: Improper Validation of Syntactic Correctness of Input
A flaw was found in Keycloak. A remote, unauthenticated attacker can send a specially crafted XML input to the Security Assertion Markup Language (SAML) endpoint. This malicious input can cause high CPU usage and worker thread starvation, leading to a Denial o
- 8.1 High severity
Red Hat build of Keycloak 26.2: Incorrect Behavior Order: Authorization Before Parsing and Canonicalization
A flaw was found in Keycloak. An authenticated user with the uma_protection role can bypass User-Managed Access (UMA) policy validation. This allows the attacker to include resource identifiers owned by other users in a policy creation request, even if the URL
- 7.5 High severity
Red Hat build of Keycloak 26.2: Excessive Platform Resource Consumption within a Loop
A flaw was found in Keycloak. An unauthenticated attacker can exploit this vulnerability by sending a specially crafted POST request with an excessively long scope parameter to the OpenID Connect (OIDC) token endpoint. This leads to high resource consumption a
- 7.4 High severity
Red Hat build of Keycloak 26.2: Improper Isolation or Compartmentalization
A flaw was found in Keycloak. The SingleUseObjectProvider, a global key-value store, lacks proper type and namespace isolation. This vulnerability allows an unauthenticated attacker to forge authorization codes. Successful exploitation can lead to the creation
- 7.3 High severity
Red Hat build of Keycloak 26.2: URL Redirection to Untrusted Site
A flaw was found in Keycloak. This issue allows an attacker, who controls another path on the same web server, to bypass the allowed path in redirect Uniform Resource Identifiers (URIs) that use a wildcard. A successful attack may lead to the theft of an acces
- 7.2 High severity
Red Hat build of Keycloak 26.4: Incorrect Privilege Assignment
A flaw was found in Keycloak. An administrator with `manage-clients` permission can exploit a misconfiguration where this permission is equivalent to `manage-permissions`. This allows the administrator to escalate privileges and gain control over roles, users,
- 8.1 High severity
Red Hat build of Keycloak 26.2: Missing Authentication for Critical Functionality
A flaw was found in Keycloak. A remote attacker could bypass security controls by sending a valid SAML response from an external Identity Provider (IdP) to the Keycloak SAML endpoint for IdP-initiated broker logins. This allows the attacker to complete broker
- 7.7 High severity
Red Hat build of Keycloak 26.2: Improper Validation of Specified Type of Input
A flaw was found in Keycloak. Keycloak's Security Assertion Markup Language (SAML) broker endpoint does not properly validate encrypted assertions when the overall SAML response is not signed. An attacker with a valid signed SAML assertion can exploit this by
- 8.8 High severity
Red Hat build of Keycloak 26.2: Authentication Bypass by Primary Weakness
A flaw was found in org.keycloak.broker.saml. When a disabled Security Assertion Markup Language (SAML) client is configured as an Identity Provider (IdP)-initiated broker landing target, it can still complete the login process and establish a Single Sign-On (
- 8.1 High severity
Red Hat build of Keycloak 26.4: Incorrect Authorization
A security flaw in the IdentityBrokerService.performLogin endpoint of Keycloak allows authentication to proceed using an Identity Provider (IdP) even after it has been disabled by an administrator. An attacker who knows the IdP alias can reuse a previously gen
- 7.3 High severity
Red Hat JBoss Enterprise Application Platform 7: Improper Neutralization of Input During Web Page Generation
A vulnerability was found in Wildfly, where a user may perform Cross-site scripting in the Wildfly deployment system. This flaw allows an attacker or insider to execute a deployment with a malicious payload, which could trigger undesired behavior against the s
- 7.1 High severity
Red Hat Build of Keycloak: Session Fixation
A session fixation issue was discovered in the SAML adapters provided by Keycloak. The session ID and JSESSIONID cookie are not changed at login time, even when the turnOffChangeSessionIdOnLogin option is configured. This flaw allows an attacker who hijacks th
- 7.5 High severity
HawtIO 4.0.0 for Red Hat build of Apache Camel 4: Concurrent Execution using Shared Resource with Improper Synchronization
A vulnerability was found in Undertow where the ProxyProtocolReadListener reuses the same StringBuilder instance across multiple requests. This issue occurs when the parseProxyProtocolV1 method processes multiple requests on the same HTTP connection. As a resu
- 8.8 High severity
Red Hat build of Keycloak 22: Improper Authentication
A flaw was found in Keycloak that occurs from an error in the re-authentication mechanism within org.keycloak.authentication. This flaw allows hijacking an active Keycloak session by triggering a new authentication process with the query parameter "prompt=logi
- 8.1 High severity
Migration Toolkit for Runtimes 1 on RHEL 8: Improper Limitation of a Pathname to a Restricted Directory
A flaw was found in Keycloak, where it does not properly validate URLs included in a redirect. This issue could allow an attacker to construct a malicious request to bypass validation and access other URLs and sensitive information within the domain or conduct