CVE-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 higher.
Does this matter?
Lower severity and a low EPSS score (0.99%). Track it; it rarely justifies an emergency change on its own.
Description
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.
- CVSS 3.1
- 6.5 MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- EPSS
- 0.99% probability · 62th percentile
- Public exploits
- None in Exploit-DB
- CISA KEV
- Not listed
- Weakness
- CWE-117, CWE-532
- Affected
- redhat/openshift container platform
- Source
- secalert@redhat.com
EPSS 1.0% since 27 October 2026; no change recorded yet. Points are recorded when the score first appears and whenever it moves by a percentage point or more.
References
- https://access.redhat.com/errata/RHSA-2019:4082Vendor Advisory
- https://access.redhat.com/errata/RHSA-2019:4088
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10213Issue Tracking, Patch, Vendor Advisory
- https://access.redhat.com/errata/RHSA-2019:4082Vendor Advisory
- https://access.redhat.com/errata/RHSA-2019:4088
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10213Issue Tracking, Patch, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.