Single Sign OnApplication · Redhat
CVE-2017-12159
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIt 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe CSRF prevention cookie in Keycloak was not generated uniquely for each user session, allowing attackers to potentially hijack authenticated sessions by predicting or stealing the static cookie value.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Single Sign OnApplication
= 7.0= 7.1all versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Keycloak or RH-SSO versionCheck the product version from the installation directory, startup logs, or admin console. For RH-SSO, check /opt/rh/rh-sso7/ or the version displayed in the admin console. For Keycloak, check the version from the server startup logs or the 'about' section in the admin console.Affected if The installed version is Red Hat Single Sign-On 7.0 or 7.1, or any version of Keycloak (the vulnerability exists in all Keycloak versions before the security fix)
-
Confirm the product typeDetermine whether the deployment is Red Hat Single Sign-On or upstream Keycloak. RH-SSO versions are separate from Keycloak versions despite shared code ancestry.Affected if Using Red Hat Single Sign-On 7.0 or 7.1 places you directly in the affected version range
-
Verify CSRF cookie behavior (if accessible)Log into the application, open browser developer tools, locate the CSRF prevention cookie (commonly named KEYCLOAK_CSRF or similar), log out and log back in, then compare the cookie value. If the value remains identical across sessions, the vulnerability is present.Affected if The CSRF cookie value is static and does not change between user sessions
You are affected if running Red Hat Single Sign-On version 7.0 or 7.1, or any version of Keycloak where the CSRF prevention cookie remains unchanged between different user sessions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Keycloak to the patched version where CSRF tokens are unique per session, and rotate any potentially compromised sessions.
Fix this in Single Sign On
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12159 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-12159 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data