CVE-2017-12160: It was found that Keycloak oauth would permit an authenticated resource to obtain an access/refresh token pair from the authentication…
Noroxi assessment
Priority: Monitor (action score 29/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: 1.9% (FIRST EPSS); higher than 80.2% of all records.
- 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.
- Fixed version: org.keycloak:keycloak-parent (Maven) 3.3.0.Final; 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.3.0.Final; 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 Keycloak oauth would permit an authenticated resource to obtain an access/refresh token pair from the authentication server, permitting indefinite usage in the case of permission revocation. An attacker on an already compromised resource could use this flaw to grant himself continued permissions and possibly conduct further attacks.
- Published
- Oct 26, 2017
- Updated
- Jun 16, 2026
- EPSS
- 1.9% · 80th percentile
- CWE
- CWE-285
Report tools
Action score
29
Low priority for now.
- CVSS
- 28 / 40 · 7.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.9%
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 |
|---|---|---|
| redhat | keycloak | cpe:2.3:a:redhat:keycloak |
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.
- redhat keycloakall versions
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.3.0.Final | 3.3.0.Final |
| 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
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…39Monitor
Published before and after this one in the same product
- Later →CVE-2016-8629Mar 12, 2018 · Red Hat Keycloak before version 2.4.0 did not correctly check permissions when handling service account user deletion requests sent to the…27Monitor
- Later →CVE-2017-2585Mar 12, 2018 · Red Hat Keycloak before version 2.5.1 has an implementation of HMAC verification for JWS tokens that uses a method that runs in…24Monitor
- Later →CVE-2018-10912Jul 23, 2018 · keycloak before version 4.0.0.final is vulnerable to a infinite loop in session replacement.19Monitor
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.3.0.Final | 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.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-285 · Improper AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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)
- Accessing Functionality Not Properly Constrained by ACLsCAPEC-1likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Directory IndexingCAPEC-127likelihood: High · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- Using Malicious FilesCAPEC-17likelihood: High · Very High
- Manipulating Opaque Client-based Data TokensCAPEC-39likelihood: High · Medium
- Bypassing ATA Password SecurityCAPEC-402
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
- Data from Local SystemT1005
- Query RegistryT1012
- File and Directory DiscoveryT1083
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Unsecured Credentials: Credentials in RegistryT1552.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Data Manipulation: Transmitted Data ManipulationT1565.002
- Hijack Execution Flow: Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
- Hijack Execution Flow: ServicesFile Permissions WeaknessT1574.010
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.