CVE-2016-8629: Red Hat Keycloak before version 2.4.0 did not correctly check permissions when handling service account user deletion requests sent to the…
Noroxi assessment
Priority: Monitor (action score 27/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% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: org.keycloak:keycloak-core (Maven) 2.4.0; rh-sso7 (Red Hat:red_hat_single_sign_on:7::el6) 0:1-2.jbcs.el6; rh-sso7-freemarker (Red Hat:red_hat_single_sign_on:7::el6) 0:2.3.23-1.redhat_2.2.jbcs.el6.
Low priority for now. Upgrade to org.keycloak:keycloak-core (Maven) 2.4.0; rh-sso7 (Red Hat:red_hat_single_sign_on:7::el6) 0:1-2.jbcs.el6; rh-sso7-freemarker (Red Hat:red_hat_single_sign_on:7::el6) 0:2.3.23-1.redhat_2.2.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
Red Hat Keycloak before version 2.4.0 did not correctly check permissions when handling service account user deletion requests sent to the rest server. An attacker with service account authentication could use this flaw to bypass normal permissions and delete users in a separate realm.
- Published
- Mar 12, 2018
- Updated
- Jun 16, 2026
- EPSS
- 1.9% · 80th percentile
- CWE
- CWE-284
Report tools
Action score
27
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 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 |
| 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
- 2.4.0affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat keycloakbefore 2.4.0
- redhat single sign on7.1
- redhat single sign on7.2
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-core | before 2.4.0 | 2.4.0 |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7 | before 0:1-2.jbcs.el6 | 0:1-2.jbcs.el6 |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-freemarker | before 0:2.3.23-1.redhat_2.2.jbcs.el6 | 0:2.3.23-1.redhat_2.2.jbcs.el6 |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-javapackages-tools | before 0:3.4.1-5.15.3.jbcs.el6 | 0:3.4.1-5.15.3.jbcs.el6 |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-keycloak | before 0:2.5.5-2.Final_redhat_1.1.jbcs.el6 | 0:2.5.5-2.Final_redhat_1.1.jbcs.el6 |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-keycloak-server | before 0:2.5.5-2.Final_redhat_1.1.jbcs.el6 | 0:2.5.5-2.Final_redhat_1.1.jbcs.el6 |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-libunix-dbus-java | before 0:0.8.0-2.jbcs.el6 | 0:0.8.0-2.jbcs.el6 |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-libunix-dbus-java-debuginfo | before 0:0.8.0-2.jbcs.el6 | 0:0.8.0-2.jbcs.el6 |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-libunix-dbus-java-devel | before 0:0.8.0-2.jbcs.el6 | 0:0.8.0-2.jbcs.el6 |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-liquibase | before 0:3.4.1-2.redhat_2.1.jbcs.el6 | 0:3.4.1-2.redhat_2.1.jbcs.el6 |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-liquibase-core | before 0:3.4.1-2.redhat_2.1.jbcs.el6 | 0:3.4.1-2.redhat_2.1.jbcs.el6 |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-python-javapackages | before 0:3.4.1-5.15.3.jbcs.el6 | 0:3.4.1-5.15.3.jbcs.el6 |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-runtime | before 0:1-2.jbcs.el6 | 0:1-2.jbcs.el6 |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-twitter4j | before 0:4.0.4-1.redhat_3.1.jbcs.el6 | 0:4.0.4-1.redhat_3.1.jbcs.el6 |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-twitter4j-core | before 0:4.0.4-1.redhat_3.1.jbcs.el6 | 0:4.0.4-1.redhat_3.1.jbcs.el6 |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-zxing | before 0:3.2.1-1.redhat_4.1.jbcs.el6 | 0:3.2.1-1.redhat_4.1.jbcs.el6 |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-zxing-core | before 0:3.2.1-1.redhat_4.1.jbcs.el6 | 0:3.2.1-1.redhat_4.1.jbcs.el6 |
| Red Hat:red_hat_single_sign_on:7::el6 | rh-sso7-zxing-javase | before 0:3.2.1-1.redhat_4.1.jbcs.el6 | 0:3.2.1-1.redhat_4.1.jbcs.el6 |
| Red Hat:red_hat_single_sign_on:7::el7 | rh-sso7 | before 0:1-2.jbcs.el7 | 0:1-2.jbcs.el7 |
| Red Hat:red_hat_single_sign_on:7::el7 | rh-sso7-freemarker | before 0:2.3.23-1.redhat_2.2.jbcs.el7 | 0:2.3.23-1.redhat_2.2.jbcs.el7 |
| Red Hat:red_hat_single_sign_on:7::el7 | rh-sso7-javapackages-tools | before 0:3.4.1-5.15.3.jbcs.el7 | 0:3.4.1-5.15.3.jbcs.el7 |
| Red Hat:red_hat_single_sign_on:7::el7 | rh-sso7-keycloak | before 0:2.5.5-2.Final_redhat_1.1.jbcs.el7 | 0:2.5.5-2.Final_redhat_1.1.jbcs.el7 |
| Red Hat:red_hat_single_sign_on:7::el7 | rh-sso7-keycloak-server | before 0:2.5.5-2.Final_redhat_1.1.jbcs.el7 | 0:2.5.5-2.Final_redhat_1.1.jbcs.el7 |
| Red Hat:red_hat_single_sign_on:7::el7 | rh-sso7-libunix-dbus-java | before 0:0.8.0-2.jbcs.el7 | 0:0.8.0-2.jbcs.el7 |
+11
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
- ← EarlierCVE-2017-12160Oct 26, 2017 · It was found that Keycloak oauth would permit an authenticated resource to obtain an access/refresh token pair from the authentication…29Monitor
- 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-core | 2.4.0 | Package registry (OSV) |
| red hat:rh-sso7 | 0:1-2.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6 | Package registry (OSV) |
| red hat:rh-sso7-freemarker | 0:2.3.23-1.redhat_2.2.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6 | Package registry (OSV) |
| red hat:rh-sso7-javapackages-tools | 0:3.4.1-5.15.3.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6 | Package registry (OSV) |
| red hat:rh-sso7-keycloak | 0:2.5.5-2.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.5-2.Final_redhat_1.1.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6 | Package registry (OSV) |
| red hat:rh-sso7-libunix-dbus-java | 0:0.8.0-2.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6 | Package registry (OSV) |
| red hat:rh-sso7-libunix-dbus-java-debuginfo | 0:0.8.0-2.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6 | Package registry (OSV) |
| red hat:rh-sso7-libunix-dbus-java-devel | 0:0.8.0-2.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6 | Package registry (OSV) |
| red hat:rh-sso7-liquibase | 0:3.4.1-2.redhat_2.1.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6 | Package registry (OSV) |
| red hat:rh-sso7-liquibase-core | 0:3.4.1-2.redhat_2.1.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6 | Package registry (OSV) |
| red hat:rh-sso7-python-javapackages | 0:3.4.1-5.15.3.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6 | Package registry (OSV) |
| red hat:rh-sso7-runtime | 0:1-2.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.
- A low-privileged account is enough.
- 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-284 · Improper Access ControlCVSS vector
CVSS:3.0/AV:N/AC:L/PR:L/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)
- Embedding Scripts within ScriptsCAPEC-19likelihood: High · High
- Malicious Logic InsertionCAPEC-441likelihood: Medium · High
- Modification of Windows Service ConfigurationCAPEC-478likelihood: Low · High
- Malicious Root CertificateCAPEC-479likelihood: Low · Low
- Intent SpoofCAPEC-502
- WebView ExposureCAPEC-503
- Data Injected During ConfigurationCAPEC-536likelihood: Low · High
- Incomplete Data Deletion in a Multi-Tenant EnvironmentCAPEC-546likelihood: Low · Medium
ATT&CK techniques
- RootkitT1014
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Initialization ScriptsT1037
- Taint shared contentT1080
- Server Software Component: Terminal Services DLLT1505.005
- Pre-OS Boot:BootkitT1542.003
- Create or Modify System ProcessT1543
- Create or Modify System Process: Launch AgentT1543.001
- Create or Modify System Process:Windows ServiceT1543.003
- Create or Modify System Process: Launch DaemonT1543.004
- Event Triggered Execution:Change Default File AssociationT1546.001
- Event Triggered Execution:.bash_profile and .bashrcT1546.004
- Event Triggered Execution: Accessibility FeaturesT1546.008
- Event Triggered Execution: Installer PackagesT1546.016
- Boot or Logon Autostart ExecutionT1547
- Boot or Logon Autostart Execution:Kernel Modules and ExtensionsT1547.006
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.