Page 10 of 58 results (0.038 seconds)

CVSS: 6.5EPSS: 0%CPEs: 2EXPL: 0

A vulnerability was found in keycloak before 6.0.2. The X.509 authenticator supports the verification of client certificates through the CRL, where the CRL list can be obtained from the URL provided in the certificate itself (CDP) or through the separately configured path. The CRL are often available over the network through unsecured protocols ('http' or 'ldap') and hence the caller should verify the signature and possibly the certification path. Keycloak currently doesn't validate signatures on CRL, which can result in a possibility of various attacks like man-in-the-middle. Se encontró una vulnerabilidad en keycloak versión anterior a 6.0.2. • http://www.securityfocus.com/bid/108748 https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3875 https://access.redhat.com/security/cve/CVE-2019-3875 https://bugzilla.redhat.com/show_bug.cgi?id=1690628 • CWE-295: Improper Certificate Validation CWE-345: Insufficient Verification of Data Authenticity •

CVSS: 5.5EPSS: 0%CPEs: 2EXPL: 0

It was found that Keycloak's Node.js adapter before version 4.8.3 did not properly verify the web token received from the server in its backchannel logout . An attacker with local access could use this to construct a malicious web token setting an NBF parameter that could prevent user access indefinitely. Se encontró que el adaptador Node.js de Keycloak antes de la versión 4.8.3 no verificó correctamente el token web recibido del servidor en su cierre de sesión de backchannel. Un atacante con acceso local podría usar esto para construir un token web malicioso que establezca un parámetro NBF que podría impedir el acceso de los usuarios de forma indefinida. It was found that Keycloak's Node.js adapter did not properly verify the web token received from the server in its backchannel logout. • http://www.securityfocus.com/bid/108734 https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10157 https://access.redhat.com/security/cve/CVE-2019-10157 https://bugzilla.redhat.com/show_bug.cgi?id=1702953 • CWE-287: Improper Authentication CWE-345: Insufficient Verification of Data Authenticity •

CVSS: 5.5EPSS: 0%CPEs: 1EXPL: 0

Keycloak up to version 6.0.0 allows the end user token (access or id token JWT) to be used as the session cookie for browser sessions for OIDC. As a result an attacker with access to service provider backend could hijack user’s browser session. Keycloak hasta la versión 6.0.0 permite utilizar el token de usuario final (JWT de token de acceso o id) como cookie de sesión para sesiones de navegador para OIDC. Como resultado, un atacante con acceso al backend del proveedor de servicios podría secuestrar la sesión del navegador del usuario. • http://www.securityfocus.com/bid/108061 https://access.redhat.com/errata/RHSA-2019:1140 https://access.redhat.com/errata/RHSA-2019:2998 https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3868 https://access.redhat.com/security/cve/CVE-2019-3868 https://bugzilla.redhat.com/show_bug.cgi?id=1679144 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •

CVSS: 8.1EPSS: 0%CPEs: 1EXPL: 0

The SAML broker consumer endpoint in Keycloak before version 4.6.0.Final ignores expiration conditions on SAML assertions. An attacker can exploit this vulnerability to perform a replay attack. El endpoint del cliente del bróker SAML en Keycloak en versiones anteriores a la 4.6.0.Final ignora las condiciones de expiración en las aserciones SAML. Un atacante podría explotar esta vulnerabilidad para realizar un ataque de repetición. • https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-14637 https://access.redhat.com/security/cve/CVE-2018-14637 https://bugzilla.redhat.com/show_bug.cgi?id=1627851 • CWE-285: Improper Authorization CWE-287: Improper Authentication •

CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0

It was found that when Keycloak before 2.5.5 receives a Logout request with a Extensions in the middle of the request, the SAMLSloRequestParser.parse() method ends in a infinite loop. An attacker could use this flaw to conduct denial of service attacks. Se ha encontrado que cuando Keycloak en versiones anteriores a la 2.5.5 recibe una solicitud Logout con un Extensions en el medio de la solicitud, el método SAMLSloRequestParser.parse() termina en un bucle infinito. Un atacante podría utilizar este fallo para realizar ataques de denegación de servicio (DoS). • http://www.securityfocus.com/bid/96882 https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2646 • CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') •