Description

It was found that the keycloak before 2.3.0 did not implement authentication flow correctly. An attacker could use this flaw to construct a phishing URL, from which he could hijack the user's session. This could lead to information disclosure, or permit further possible attacks.

Remediation

References

http://rhn.redhat.com/errata/RHSA-2016-2945.html

http://www.securityfocus.com/bid/95070

http://www.securitytracker.com/id/1037460

https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-8609

Related Vulnerabilities

CVE-2023-47323 Vulnerability in maven package org.silverpeas.core:silverpeas-core-web

CVE-2018-15758 Vulnerability in maven package org.springframework.security.oauth:spring-security-oauth2

CVE-2023-23850 Vulnerability in maven package org.jenkins-ci.plugins:synopsys-coverity

CVE-2022-23631 Vulnerability in npm package superjson

CVE-2020-2132 Vulnerability in maven package com.parasoft:environment-manager

Severity

Critical

Classification

CWE-384 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Tags

Vendor Advisory Third Party Advisory VDB Entry Issue Tracking