KeycloakApplication · Redhat
CVE-2019-14832
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 REST API before version 8.0.0 where it would permit user access from a realm the user was not configured. An authenticated attacker with knowledge of a user id could use this flaw to access unauthorized information or to carry out 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 confidenceThis is an authorization bypass vulnerability in Keycloak's REST API versions before 8.0.0. The API failed to properly validate whether an authenticated user was authorized to access resources in a specific realm, allowing any authenticated user with knowledge of a target user ID to access that user's information across realms they were not assigned to.
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
< 7.0.1CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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 through the admin console, startup logs, or by querying the /auth/realms/master endpoint (for older versions) or /realms/master (for newer versions). The version is typically displayed in the server output at startup or in the server info endpoint.Affected if The version displayed is earlier than 8.0.0, or for Red Hat Keycloak earlier than 7.0.1
-
Verify REST API accessibilityConfirm the Keycloak REST API endpoints are network-accessible. This typically involves checking if ports 8080 or 8443 (default Keycloak ports) are listening and reachable from where API clients would connect.Affected if The REST API is exposed and reachable by authenticated users
-
Confirm authentication is enabledVerify that Keycloak authentication is required to access the REST API endpoints. Attempt an unauthenticated request to the users endpoint to confirm the server rejects it, then authenticate and retry to confirm access is granted to valid users.Affected if Unauthenticated requests are properly rejected but authenticated users can make API calls
-
Test cross-realm user accessAs an authenticated user in one realm, attempt to query user information in a different realm using the REST API (for example, GET /auth/realms/{other-realm}/users/{target-user-id}) using a known user ID from that other realm.Affected if The API returns user information from a realm where the authenticated user has no assignments, confirming the authorization bypass is present
A user is affected if their Keycloak installation version is earlier than 8.0.0 (or Red Hat Keycloak earlier than 7.0.1) AND the REST API is accessible to authenticated users, allowing unauthorized cross-realm user data access.
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 data7.0.1
Upgrade Keycloak to version 8.0.0 or later, which contains the fix for this authorization flaw.
Fix this in Keycloak
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14832 — 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-14832 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