keycloak: account hijacking via auth code fixation
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 |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Single Sign-On 7.0 | |||
| cpe:/a:redhat:jboss_single_sign_on:7.0 | RHSA-2016:2945 | 2016-12-13T00:00:00Z | |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2018-0559 | 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. |
Github GHSA |
GHSA-95m6-mjh3-58gm | Improper Authentication in org.keycloak:keycloak-core |
No CVSS v4.0
No CVSS v3.1
This CVE is not in the KEV list.
Exploit prediction score: 1.7% (1.679% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.