A flaw was found in Keycloak before 13.0.0 where an external identity provider, after successful authentication, redirects to a Keycloak end
A flaw was found in Keycloak before 13.0.0 where an external identity provider, after successful authentication, redirects to a Keycloak endpoint that accepts multiple invocations with the use of the same "state" parameter. This flaw allows a malicious user to perform replay attacks.
- Published
- Dec 15, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.0% · 62th percentile
- CWE
- CWE-294
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
19
Monitor
Low priority for now.
- CVSS
- 19 / 40 · 4.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| redhat | keycloak | cpe:2.3:a:redhat:keycloak |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat keycloakbefore 13.0.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
n/a keycloak
- keycloak 13.0.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-keycloak | before 0:9.0.12-1.redhat_00001.1.el6sso | 0:9.0.12-1.redhat_00001.1.el6sso |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-keycloak-server | before 0:9.0.12-1.redhat_00001.1.el6sso | 0:9.0.12-1.redhat_00001.1.el6sso |
| Red Hat:red_hat_single_sign_on:7::el7 | rh-sso7-keycloak | before 0:9.0.12-1.redhat_00001.1.el7sso | 0:9.0.12-1.redhat_00001.1.el7sso |
| Red Hat:red_hat_single_sign_on:7::el7 | rh-sso7-keycloak-server | before 0:9.0.12-1.redhat_00001.1.el7sso | 0:9.0.12-1.redhat_00001.1.el7sso |
| Red Hat:red_hat_single_sign_on:7::el8 | rh-sso7-keycloak | before 0:9.0.12-1.redhat_00001.1.el8sso | 0:9.0.12-1.redhat_00001.1.el8sso |
| Red Hat:red_hat_single_sign_on:7::el8 | rh-sso7-keycloak-server | before 0:9.0.12-1.redhat_00001.1.el8sso | 0:9.0.12-1.redhat_00001.1.el8sso |
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-10770A flaw was found in Keycloak before 13.0.0, where it is possible to force the server to call out an unverified URL using the OIDC parameter 42Plan
- CVE-2022-1245A privilege escalation flaw was found in the token exchange feature of keycloak.39Monitor
- CVE-2019-14910A vulnerability was found in keycloak 7.x, when keycloak is configured with LDAP user federation and StartTLS is used instead of SSL/TLS fro39Monitor
- CVE-2022-3782keycloak: path traversal via double URL encoding.38Monitor
- CVE-2021-20195A flaw was found in keycloak in versions before 13.0.0.38Monitor
- CVE-2019-14837A flaw was found in keycloack before version 8.0.0.37Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| red hat:rh-sso7-keycloak | 0:9.0.12-1.redhat_00001.1.el6sso · Red Hat:red_hat_single_sign_on:7::el6 | Package registry (OSV) |
| red hat:rh-sso7-keycloak-server | 0:9.0.12-1.redhat_00001.1.el6sso · Red Hat:red_hat_single_sign_on:7::el6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-294 · Authentication Bypass by Capture-replayCVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Session SidejackingCAPEC-102likelihood: High · High
- KerberoastingCAPEC-509High
- Remote Services with Stolen CredentialsCAPEC-555Very High
- Windows Admin Shares with Stolen CredentialsCAPEC-561
- Reusing Session IDs (aka Session Replay)CAPEC-60likelihood: High · High
- Use of Captured Hashes (Pass The Hash)CAPEC-644likelihood: Medium · High
- Use of Captured Tickets (Pass The Ticket)CAPEC-645likelihood: Low · High
- Use of Known Kerberos CredentialsCAPEC-652likelihood: Medium · High
ATT&CK techniques
- Remote ServicesT1021
- Remote Services:SMB/Windows Admin SharesT1021.002
- Email Collection:Remote Email CollectionT1114.002
- External Remote ServicesT1133
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Use Alternate Authentication Material:Pass The HashT1550.002
- Use Alternate Authentication Material:Pass The TicketT1550.003
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Adversary-in-the-MiddleT1557
- Steal or Forge Kerberos TicketsT1558
- Steal or Forge Kerberos Tickets:KerberoastingT1558.003
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.