CVE-2019-10213 json
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 operato…
published 2019-11-25 6 y ago modified 2026-06-17 4 mo ago also EUVD-2019-2229
- cvss
- 5.3
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 62%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2019-10213 updated cvss 5.3
openshift: Secret data written to pod logs when operator set at Debug level or higher
-
Red Hat OpenShift Container Platform 4 library-goaffected: no fix available
-
Red Hat OpenShift Container Platform 4.1 openshift4/ose-console-operator v4.1.16-201909100604, openshift4/ose-cluster-config-operator v4.1.26-201911260202, openshift4/ose-cluster-authentication-operator v4.1.26-201911260202, openshift4/ose-cluster-kube-apiserver-operator v4.1.26-201911260202, openshift4/ose-cluster-openshift-apiserver-operator v4.1.27-201912030019fixed: vendor fix RHSA-2019:4082
-
Red Hat OpenShift Container Platform 4.2 openshift4/ose-cli v4.2.0-201910101614, openshift4/ose-pod v4.2.0-201910101614, openshift4/ose-etcd v4.2.0-201910101614, openshift4/ose-node v4.2.0-201910101614, openshift4/ose-tests v4.2.0-201910101614, openshift4/ose-console v4.2.0-201910101614, +91 morefixed: vendor fix RHBA-2019:2922
-
Red Hat OpenShift Container Platform 3.9 library-go Red Hat OpenShift Container Platform 3.10 library-go Red Hat OpenShift Container Platform 3.11 library-gonot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.99% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 5.3 | CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Affected products
- Red Hat openshift
Classification
References
-
bugzilla.redhat.com
/show_bug.cgi?id=CVE-2019-10213
issue-tracking, patch, vendor-advisory
-
access.redhat.com
/errata/RHSA-2019:4082
vendor-advisory
-
access.redhat.com
/errata/RHSA-2019:4088
vendor-advisory
Sources
- CVE List CVE-2019-10213
- NVD CVE-2019-10213
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.