KeycloakApplication · Redhat
CVE-2019-10170
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 · uneditedA flaw was found in the Keycloak admin console, where the realm management interface permits a script to be set via the policy. This flaw allows an attacker with authenticated user and realm management permissions to configure a malicious script to trigger and execute arbitrary code with the permissions of the application user.
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 confidenceKeycloak admin console's realm management interface allows authenticated users with realm management permissions to configure and execute arbitrary scripts through the policy system. This script execution runs with the permissions of the application user, enabling privilege escalation and potential full system compromise.
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
KeycloakApplication
< 8.0.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 installed Keycloak versionCheck the Keycloak server version by reviewing startup logs, the admin console 'Server Info' page, or the manifest files in the Keycloak installation directoryAffected if The installed version is Redhat Keycloak below version 8.0.0
-
Verify admin console accessibilityConfirm the Keycloak admin console (typically at /auth/admin/ or /admin/) is reachable and determines if unauthenticated or low-privilege users could access realm management interfacesAffected if The admin console is exposed to untrusted users or networks
-
Review authorization policies for script executionInspect all authorization policies in each realm through the realm settings > authorization tab, looking for policies that execute JavaScript or other scriptsAffected if Any authorization policy is configured to run arbitrary scripts, especially policies authored by untrusted users
-
Audit realm management role assignmentsCheck which users or groups are assigned the 'realm-management' client role or equivalent elevated permissions in the realm's user managementAffected if Users with realm management permissions exist who should not have administrative access
-
Examine existing scripts in authorization resourcesNavigate to the realm's resources and policies sections in the admin console, reviewing any script-based authorization resources for suspicious or unauthorized codeAffected if Any scripts exist that were not created by trusted administrators or contain malicious logic
You are affected if running Redhat Keycloak version below 8.0.0 AND the admin console is accessible to users with realm management permissions who may have configured unauthorized script-based policies
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 data8.0.0
Update Keycloak to the latest patched version and audit all realm policies for any unauthorized or malicious script configurations. Restrict admin console permissions to only trusted administrators.
Fix this in Keycloak
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10170 — 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-2019-10170 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