Skip to content
Fencer Intel
medium 5.3

CVE-2019-14854 json

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 De…

published 6y ago modified 4mo ago also EUVD-2019-5976

cvss
5.3
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

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.

Is CVE-2019-14854 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-14854 updated cvss 5.3

library-go: Secret data written to static pod logs when operator set at Debug level or higher

  • Red Hat OpenShift Container Platform 4 library-go
    affected: no fix available
  • Red Hat OpenShift Container Platform 4.1 openshift4/ose-cluster-kube-apiserver-operator v4.1.26-201911260202, openshift4/ose-cluster-kube-scheduler-operator v4.1.27-201912030019, openshift4/ose-cluster-kube-controller-manager-operator v4.1.27-201912030019
    fixed: vendor fix RHSA-2019:4081
  • Red Hat OpenShift Container Platform 4.2 openshift4/ose-cluster-kube-apiserver-operator v4.2.9-201911261133, openshift4/ose-cluster-kube-scheduler-operator v4.2.9-201911261133, openshift4/ose-cluster-kube-controller-manager-operator v4.2.10-201912022352
    fixed: vendor fix RHSA-2019:4075

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.80% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-14854 referenced PoC, tagged "exploit" by a source, unverified

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 library-go

Classification

Weakness
  • CWE-117 Improper Output Neutralization for Logs
  • CWE-532 Insertion of Sensitive Information into Log File

References

Sources

Fencer Intel 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.