CVE-2019-10213
published 2019-11-25CVE-2019-10213: OpenShift Container Platform, versions 4.1 and 4.2, does not sanitize secret data written to pod logs when the log level in a given operator is set to Debug or…
PriorityP432medium6.5CVSS 3.1
AVNACLPRLUINSUCHINAN
EPSS
0.99%
59.0th percentile
OpenShift Container Platform, versions 4.1 and 4.2, does not sanitize secret data written to pod logs when the log level in a given operator is set to Debug or higher. A low privileged user could read pod logs to discover secret material if the log level has already been modified in an operator by a privileged user.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| red_hat | openshift | — | — |
| redhat | openshift_container_platform | — | — |
| redhat | openshift_container_platform | — | — |
CVSS provenance
nvdv3.16.5MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvdv3.05.3MEDIUMCVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
nvdv2.04.0MEDIUMAV:N/AC:L/Au:S/C:P/I:N/A:N
vendor_redhat6.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
openshift: Secret data written to pod logs when operator set at Debug level or higher
vendor_redhat·2019-07-12·CVSS 6.5
CVE-2019-10213 [MEDIUM] CWE-117 openshift: Secret data written to pod logs when operator set at Debug level or higher
openshift: Secret data written to pod logs when operator set at Debug level or higher
OpenShift Container Platform, versions 4.1 and 4.2, does not sanitize secret data written to pod logs when the log level in a given operator is set to Debug or higher. A low privileged user could read pod logs to discover secret material if the log level has already been modified in an operator by a privileged user.
Package: library-go (Red Hat OpenShift Container Platform 3.10) - Not affected
Package: library-go (Red Hat OpenShift Container Platform 3.11) - Not affected
Package: library-go (Red Hat OpenShift Container Platform 3.9) - Not affected
Package: library-go (Red Hat OpenShift Container Platform 4) - Affected
Package: openshift4/ose-cluster-kube-controller-manager-operator (Red Hat OpenShif
GHSA
Sensitive Data Exposure in Openshift Container Platform
ghsa_unreviewed·2021-05-17
CVE-2019-10213 [MEDIUM] CWE-117 Sensitive Data Exposure in Openshift Container Platform
Sensitive Data Exposure in Openshift Container Platform
OpenShift Container Platform, versions 4.1 and 4.2, does not sanitize secret data written to pod logs when the log level in a given operator is set to Debug or higher. A low privileged user could read pod logs to discover secret material if the log level has already been modified in an operator by a privileged user.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-14854 library-go: Secret data written to static pod logs when operator set at Debug level or higher
bugzilla·2019-10-07·CVSS 6.5
CVE-2019-14854 [MEDIUM] CVE-2019-14854 library-go: Secret data written to static pod logs when operator set at Debug level or higher
CVE-2019-14854 library-go: Secret data written to static pod logs when operator set at Debug level or higher
OpenShift Container Platform 4 does not sanitize secret data written to static pod logs when the log level in a given operator is set to Debug or higher. A low privileged user could read pod logs to discover secret material if the log level has already been modified in an operator by a privileged user.
This is similar to CVE-2019-10213 but different in that it only affects operators that create and manage static pods.
Discussion:
This issue has been addressed in the following products:
Red Hat OpenShift Container Platform 4.2
Via RHSA-2019:4075 https://access.redhat.com/errata/RHSA-2019:4075
---
This bug is now closed. Further updates for individual products will be reflecte
Bugzilla
CVE-2019-10213 openshift: Secret data written to pod logs when operator set at Debug level or higher
bugzilla·2019-07-31·CVSS 6.5
CVE-2019-10213 [MEDIUM] CVE-2019-10213 openshift: Secret data written to pod logs when operator set at Debug level or higher
CVE-2019-10213 openshift: Secret data written to pod logs when operator set at Debug level or higher
OpenShift Container Platform 4 does not sanitize secret data written to pod logs when the log level in a given operator is set to Debug or higher. A low privileged user could read pod logs to discover secret material if the log level has already been modified in an operator by a privileged user.
Upstream Fix:
https://github.com/openshift/library-go/pull/472
Discussion:
Flaw introduced by:
https://github.com/openshift/library-go/pull/244
---
This issue has been addressed in the following products:
Red Hat OpenShift Container Platform 4.1
Via RHSA-2019:2791 https://access.redhat.com/errata/RHSA-2019:2791
---
This bug is now closed. Further updates for individual products will be
https://access.redhat.com/errata/RHSA-2019:4082https://access.redhat.com/errata/RHSA-2019:4088https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10213https://access.redhat.com/errata/RHSA-2019:4082https://access.redhat.com/errata/RHSA-2019:4088https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10213
2019-11-25
Published