dbcve.org
Openshift Container PlatformApplication · Redhat

CVE-2020-10706

MEDIUM · 6.6 CVSS v3.1 Published 2020-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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 OpenShift Container Platform where OAuth tokens are not encrypted when the encryption of data at rest is enabled. This flaw allows an attacker with access to a backup to obtain OAuth tokens and then use them to log into the cluster as any user who logged into the cluster via the WebUI or via the command line in the last 24 hours. Once the backup is older than 24 hours the OAuth tokens are no longer valid.

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

In OpenShift Container Platform, OAuth tokens are stored unencrypted even when data-at-rest encryption is enabled. An attacker with access to a cluster backup can extract these tokens and authenticate as any user who logged in via WebUI or CLI within the prior 24-hour window.

MitigationRestrict backup access to authorized personnel, ensure backups are encrypted at rest and in transit, and rotate OAuth tokens immediately following any suspected 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
Openshift Container PlatformApplication
Affected:all versions

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
Physical
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Confirm OpenShift Container Platform is in use
    Run 'oc get clusterversion' or check the OpenShift web console for the version information
    Affected if The environment is running any version of Red Hat OpenShift Container Platform
  2. Identify OAuth token storage location
    Check the OAuth deployment configuration with 'oc get oauthcluster -o yaml' and review the 'oauth-config' for token storage settings
    Affected if OAuth tokens are being stored in the cluster's etcd database without encryption
  3. Review backup encryption status
    Examine cluster backup files and check if they are encrypted at rest using the storage backend's encryption features; check backup manifest files for encryption indicators
    Affected if Backups exist and are stored without encryption or the backup encryption is not properly configured
  4. Audit backup file access controls
    List file permissions on etcd backup directories (typically in /etc/kubernetes/static-pod-resources/etcd-pod-*/etcd-backup/); run 'ls -la' and verify only authorized service accounts have read access
    Affected if Backup files have weak permissions allowing unauthorized access to service accounts or users outside the cluster admin group
  5. Check for signs of unauthorized backup access
    Review audit logs for etcd for any unexpected read operations on secret or token resources; search for 'authentication-oauth' events in 'oc get events --all-namespaces'
    Affected if There are events indicating extraction of OAuth tokens or unexpected access to secrets containing OAuth tokens

If you are running OpenShift Container Platform with unencrypted backups or weak backup access controls, your OAuth tokens could have been extracted by anyone with backup access.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict backup access to authorized personnel, ensure backups are encrypted at rest and in transit, and rotate OAuth tokens immediately following any suspected compromise.

Fix this in Openshift Container Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-10706 — 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-10706 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