CVE-2017-12159: It was found that the cookie used for CSRF prevention in Keycloak was not unique to each session.
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.7% (FIRST EPSS); higher than 86.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: org.keycloak:keycloak-parent (Maven) 3.4.0; rh-sso7-keycloak (Red Hat:red_hat_single_sign_on:7::el6) 0:2.5.14-1.Final_redhat_1.1.jbcs.el6; rh-sso7-keycloak-server (Red Hat:red_hat_single_sign_on:7::el6) 0:2.5.14-1.Final_redhat_1.1.jbcs.el6.
Low priority for now. Upgrade to org.keycloak:keycloak-parent (Maven) 3.4.0; rh-sso7-keycloak (Red Hat:red_hat_single_sign_on:7::el6) 0:2.5.14-1.Final_redhat_1.1.jbcs.el6; rh-sso7-keycloak-server (Red Hat:red_hat_single_sign_on:7::el6) 0:2.5.14-1.Final_redhat_1.1.jbcs.el6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
It was found that the cookie used for CSRF prevention in Keycloak was not unique to each session. An attacker could use this flaw to gain access to an authenticated user session, leading to possible information disclosure or further attacks.
- Published
- Oct 26, 2017
- Updated
- Jun 16, 2026
- EPSS
- 2.7% · 86th percentile
- CWE
- CWE-613
Report tools
Action score
31
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.7%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| keycloak | keycloak | cpe:2.3:a:keycloak:keycloak |
| redhat | single sign on | cpe:2.3:a:redhat:single_sign_on |
| redhat | enterprise linux server | cpe:2.3:o:redhat:enterprise_linux_server |
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.
Red Hat, Inc. keycloak
- 3.4.0affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- keycloak keycloakall versions
- redhat single sign on7.0
- redhat single sign on7.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.keycloak:keycloak-parent | before 3.4.0 | 3.4.0 |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-keycloak | before 0:2.5.14-1.Final_redhat_1.1.jbcs.el6 | 0:2.5.14-1.Final_redhat_1.1.jbcs.el6 |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-keycloak-server | before 0:2.5.14-1.Final_redhat_1.1.jbcs.el6 | 0:2.5.14-1.Final_redhat_1.1.jbcs.el6 |
| Red Hat:red_hat_single_sign_on:7::el7 | rh-sso7-keycloak | before 0:2.5.14-1.Final_redhat_1.1.jbcs.el7 | 0:2.5.14-1.Final_redhat_1.1.jbcs.el7 |
| Red Hat:red_hat_single_sign_on:7::el7 | rh-sso7-keycloak-server | before 0:2.5.14-1.Final_redhat_1.1.jbcs.el7 | 0:2.5.14-1.Final_redhat_1.1.jbcs.el7 |
Same product
keycloak: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-12161It was found that keycloak before 3.4.2 final would permit misuse of a client-side /etc/hosts entry to spoof a URL in a password reset…35Monitor
- CVE-2014-3709The org.keycloak.services.resources.SocialResource.callback method in JBoss KeyCloak before 1.0.3.Final allows remote attackers to conduct…35Monitor
- CVE-2014-3651JBoss KeyCloak before 1.0.3.Final allows remote attackers to cause a denial of service (resource consumption) via a large value in the size…30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2017-12158Oct 26, 2017 · It was found that Keycloak would accept a HOST header URL in the admin console and use it to determine web resource locations.21Monitor
- Later →CVE-2025-9162Aug 21, 2025 · Org.keycloak/keycloak-model-storage-service: variable injection into environment variables19Monitor
- Later →CVE-2025-10044Sep 5, 2025 · Keycloak: keycloak error_description injection on error pages17Monitor
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 |
|---|---|---|
| Maven:org.keycloak:keycloak-parent | 3.4.0 | Package registry (OSV) |
| red hat:rh-sso7-keycloak | 0:2.5.14-1.Final_redhat_1.1.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6 | Package registry (OSV) |
| red hat:rh-sso7-keycloak-server | 0:2.5.14-1.Final_redhat_1.1.jbcs.el6 · 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-613 · Insufficient Session ExpirationCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.