dbcve.org
Keycloak OperatorApplication · Redhat

CVE-2020-1731

CRITICAL · 9.8 CVSS v3.1 Published 2020-03-02
Fix available
A fix is available. Upgrade to 8.0.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A flaw was found in all versions of the Keycloak operator, before version 8.0.2,(community only) where the operator generates a random admin password when installing Keycloak, however the password remains the same when deployed to the same OpenShift namespace.

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 confidence

The Keycloak operator for OpenShift generates a random admin password during initial Keycloak installation, but fails to regenerate or rotate this password on subsequent deployments to the same namespace. This results in a static, predictable credential that persists across redeployments, potentially exposing the admin account if the initial password is discovered or leaked.

MitigationUpgrade the Keycloak operator to version 8.0.2 or later (community edition). For existing deployments, manually rotate the admin password to ensure it is not the predictable value from the initial deployment.

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
Keycloak OperatorApplication
Affected:< 8.0.2

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check the Keycloak operator version
    Run 'oc get subscription keycloak-operator -n <namespace> -o jsonpath={.status.currentCSV}' or 'oc get csv -n <namespace>' to find the installed operator version and name, then check the version string
    Affected if The operator version is below 8.0.2 (e.g., 7.x, 8.0.0, 8.0.1)
  2. Verify Keycloak deployment exists
    Run 'oc get keycloak -A' or 'oc get KeycloakRealm -A' to find any existing Keycloak custom resources in the cluster
    Affected if A Keycloak CR exists in any namespace
  3. Check for redeployment to the same namespace
    Run 'oc get deployment -A' and look for multiple keycloak-operator related deployments or check the Keycloak CR's generation field with 'oc get keycloak <name> -n <namespace> -o jsonpath={.metadata.generation}'
    Affected if The Keycloak instance has been deployed or redeployed more than once to the same namespace (generation > 1)
  4. Inspect admin password secret configuration
    Run 'oc get secret -A | grep -i keycloak' to find admin credentials, then check if the same secret persists across deployments by comparing creation timestamps across redeployments
    Affected if The admin password secret has not been regenerated after the initial deployment (same secret name/version persists across multiple operator reconcile cycles)

You are affected if the Keycloak operator version is below 8.0.2 AND you have performed more than one deployment to the same namespace, meaning your admin password has not rotated since initial installation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 8.0.2 or later
Fixed in 8.0.2
Interim mitigation

Upgrade the Keycloak operator to version 8.0.2 or later (community edition). For existing deployments, manually rotate the admin password to ensure it is not the predictable value from the initial deployment.

Recommended fix High confidence

Keycloak Operator 8.0.2

  1. Check the current version of the Keycloak Operator deployed in your OpenShift cluster
  2. Stop or uninstall the existing Keycloak Operator deployment
  3. Apply or install Keycloak Operator version 8.0.2 from the OperatorHub or community sources
  4. Verify the operator pod is running with the new version
  5. Re-deploy any Keycloak instances to ensure the password generation uses the fixed implementation
  6. Verify that a new random admin password is generated correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Keycloak Operator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-1731 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-1731 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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