openshift/openshift-apiserver: oauthtokens leaked to logs on panic
Published Jun 12, 2020
7.5
HIGHCVSS 3.1
EPSS 1.07%
Description
A flaw was found in the OpenShift API Server, where it failed to sufficiently protect OAuthTokens by leaking them into the logs when an API Server panic occurred. This flaw allows an attacker with the ability to cause an API Server error to read the logs, and use the leaked OAuthToken to log into the API Server with the leaked token.
Affected products
-
- Version All versionsStatusaffectedConstraints-
- Version
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Openshift | Openshift/openshift-Apiserver | n/a |
|
- 3.11
- 4.0
No data.
Red Hat OpenShift Container Platform 3.11
atomic-openshift
Will not fix
Red Hat OpenShift Container Platform 4
openshift4/ose-openshift-apiserver-rhel8
Will not fix
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift Container Platform 3.11 | atomic-openshift | Will not fix | n/a |
| Red Hat OpenShift Container Platform 4 | openshift4/ose-openshift-apiserver-rhel8 | Will not fix | n/a |
No package ranges for this CVE.
Remediation
Red Hat statement
OAuthTokens are only valid for 1 day by default.
Red Hat mitigation
Ensure the OpenShift API Server logs are kept private
Metrics
No CVSS v4.0 score for this CVE.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
1 other source (Red Hat) ▾
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
No CVSS v3.0 score for this CVE.
AV:N/AC:M/Au:S/C:P/I:P/A:P
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 3, 2026.
Score over time
2021–2026- EPSS v1
- EPSS v5
- EPSS v2
- EPSS v3
- EPSS v4
Percentile over time
- EPSS v1
- EPSS v5
- EPSS v2
- EPSS v3
- EPSS v4
Table of values (14 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 3, 2026 | 1.07% (0.01072) | 63.71th | v5 (v2026.06.15) |
| Jun 15, 2026 | 1.07% (0.01072) | 60.39th | v5 (v2026.06.15) |
| Mar 30, 2025 | 0.52% (0.00520) | 64.15th | v4 (v2025.03.14) |
| Mar 29, 2025 | 1.64% (0.01639) | 70.44th | v4 (v2025.03.14) |
| Jul 20, 2024 | 0.10% (0.00104) | 43.08th | v3 (v2023.03.01) |
| Jun 28, 2024 | 0.10% (0.00104) | 42.95th | v3 (v2023.03.01) |
| Mar 7, 2023 | 0.10% (0.00104) | 40.93th | v3 (v2023.03.01) |
| Mar 6, 2023 | 0.89% (0.00885) | 27.89th | v2 (v2022.01.01) |
| Apr 1, 2022 | 0.89% (0.00885) | 24.24th | v2 (v2022.01.01) |
| Feb 4, 2022 | 9.03% (0.09029) | 86.86th | v2 (v2022.01.01) |
| Feb 3, 2022 | 2.74% (0.02742) | 63.06th | v1 |
| Jan 6, 2022 | 2.74% (0.02742) | 62.72th | v1 |
| Jan 5, 2022 | 0.62% (0.00624) | 46.35th | v5 (v2026.06.15) |
| Apr 14, 2021 | 0.62% (0.00624) | 0.00th | v1 |
References (6)
- https://access.redhat.com/security/cve/CVE-2020-10752 Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1839942 Issue Tracking
- https://github.com/openshift/enhancements/pull/323 x_refsource_CONFIRMPatchThird Party Advisory
- https://github.com/openshift/origin/blob/master/vendor/k8s.io/kubernetes/staging/src/k8s.io/apiserver/pkg/server/filters/wrap.go#L39 x_refsource_CONFIRMThird Party Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2020-10752
- https://www.cve.org/CVERecord?id=CVE-2020-10752
| Link | Providers | Tags |
|---|---|---|
| https://access.redhat.com/security/cve/CVE-2020-10752 | Vendor Advisory | |
| https://bugzilla.redhat.com/show_bug.cgi?id=1839942 | Issue Tracking | |
| https://github.com/openshift/enhancements/pull/323 | x_refsource_CONFIRMPatchThird Party Advisory | |
| https://github.com/openshift/origin/blob/master/vendor/k8s.io/kubernetes/staging/src/k8s.io/apiserver/pkg/server/filters/wrap.go#L39 | x_refsource_CONFIRMThird Party Advisory | |
| https://nvd.nist.gov/vuln/detail/CVE-2020-10752 | ||
| https://www.cve.org/CVERecord?id=CVE-2020-10752 |
Change history (0)
No recorded changes yet.