CVE-2017-12159
UnknownEPSS 2.40%
Last modified
CVE-2017-12159 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 2.40% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Redhat | Single Sign On | 7.0 |
| Redhat | Single Sign On | 7.1 |
| Keycloak | Keycloak | All versions |
References
- http://www.securityfocus.com/bid/101601Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHSA-2017:2904Third Party Advisory
- https://access.redhat.com/errata/RHSA-2017:2905Third Party Advisory
- https://access.redhat.com/errata/RHSA-2017:2906Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1484111Issue Tracking, Third Party Advisory, VDB Entry
- http://www.securityfocus.com/bid/101601Third Party Advisory, VDB Entry
- https://access.redhat.com/errata/RHSA-2017:2904Third Party Advisory
- https://access.redhat.com/errata/RHSA-2017:2905Third Party Advisory
- https://access.redhat.com/errata/RHSA-2017:2906Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1484111Issue Tracking, Third Party Advisory, VDB Entry
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-12159?
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.
How severe is CVE-2017-12159?
Severity scoring for CVE-2017-12159 is pending analysis. The EPSS model estimates a 2.40% probability of exploitation in the next 30 days.
How do I fix CVE-2017-12159?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-12153A security flaw was discovered in the nl80211_set_rekey_data…
- CVE-2017-12154The prepare_vmcs02 function in arch/x86/kvm/vmx.c in the Lin…
- CVE-2017-12155A resource-permission flaw was found in the openstack-triple…
- CVE-2017-12156Moodle 3.x has XSS in the contact form on the "non-responden…
- CVE-2017-12157In Moodle 3.x, various course reports allow teachers to view…
- CVE-2017-12158It was found that Keycloak would accept a HOST header URL in…
- CVE-2017-12160It was found that Keycloak oauth would permit an authenticat…7.2
- CVE-2017-12161It was found that keycloak before 3.4.2 final would permit m…
- CVE-2017-12163An information leak flaw was found in the way SMB1 protocol …4.1
- CVE-2017-12164A flaw was discovered in gdm 3.24.1 where gdm greeter was no…4.1
- CVE-2017-12165It was discovered that Undertow before 1.4.17, 1.3.31 and 2.…2.6
- CVE-2017-12166OpenVPN versions before 2.3.3 and 2.4.x before 2.4.4 are vul…9.8
Are you affected by CVE-2017-12159?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST