Bug 1819011 (CVE-2020-10706)
| Summary: | CVE-2020-10706 openshift/openshift-apiserver: oauth tokens not encrypted when enabling encryption of data at rest | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | Jason Shepherd <jshepherd> |
| Component: | vulnerability | Assignee: | Nobody <nobody> |
| Status: | NEW --- | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | bmontgom, danclark, eparis, jburrell, mfojtik, nstielau, sponnaga |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: |
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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1819489, 1819490 | ||
| Bug Blocks: | 1818018 | ||
|
Description
Jason Shepherd
2020-03-30 23:38:35 UTC
Acknowledgments: Name: Stefan Schimanski (Red Hat) Mitigation: If you have made a vulnerable backup public you can revoke leaked OAuth tokens by deleting them with the OpenShift API. To be more precise, this affects OAuthAccessToken and OAuthAuthorizeToken in the auth.openshift.io API group. Statement: This issue only affects OpenShift Container Platform when the 'encryption at rest' feature enabled, see https://access.redhat.com/documentation/en-us/openshift_container_platform/4.3/html/authentication/encrypting-etcd. When backing up the encrypted data the keys should be stored separately to the data, making backups the most likely target of this attack. What is the target release to fix this vulnerability? If the entire backup disk is encrypted with something like AWS KMS that should cover this problem right? In that the entire backup would be encrypted and unusable due to KMS if it were leaked somewhere. Indeed, encrypting the entire backup is a good mitigation for this vulnerability. This has been fixed in the OCP 4.6 GA release. I'll update the metadata so the CVE page correctly links to that Errata. |