Skip to main content
No exploitation reportedFix available

CVE-2019-14819

No exploitation reported by the sources we read.

  • Published2020-01-07
  • WeaknessCWE-266 · CWE-269 · CWE-270

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

A flaw was found during the upgrade of an existing OpenShift Container Platform 3.x cluster. Using CRI-O, the dockergc service account is assigned to the current namespace of the user performing the upgrade. This flaw can allow an unprivileged user to escalate their privileges to those allowed by the privileged Security Context Constraints.

Timeline

dates in UTC
  1. 2020-01-0718:15CVE publishedNVD

Versions per branch

NVD
Redhat openshift container platform
BranchAffectedFixed in
3.10= 3.10no fix published
3.11= 3.11no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • openshift-ansibleRed Hat:openshift:3.11::el7all versions · fixed in 0:3.11.146-1.git.0.fcedb45.el7and 4 other packages

Vendor advisories

  • CVE-2019-14819 Red Hat Product Security6 products fixed · 5 known affected

    openshift-ansible: dockergc service account incorrectly associated with namespace during upgrade

    openshift-ansible as a component of Red Hat OpenShift Container Platform 3.10 · openshift-ansible-docs as a component of Red Hat OpenShift Container Platform 3.10 · openshift-ansible-playbooks as a component of Red Hat OpenShift Container Platform 3.10 · +2 more

  • RHSA-2019:2818 Red Hat Product Security6 products fixed

    Red Hat Security Advisory: OpenShift Container Platform 3.11 security update

Full record on NVD

Fix

  1. Vendor fix Red Hat Product Security RHSA-2019:2818 · 6 productsSee the following documentation, which will be updated shortly for release 3.11.146, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html
  2. Workaround from the vendor Red Hat Product Security RHSA-2019:2818 · 6 productsMake sure your kubeconfig (~/.kube/config) is using the 'default' context when executing, or re-executing a cluster upgrade or install using the ansible playbooks.
  3. No fix available, says the vendor Red Hat Product Security CVE-2019-14819 · 5 productsAffected

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVSS 3.18.8read 2026-10-23
  • CNACVSS 3.07.5known since 2026-10-23
  • NVDCVSS 2.06.5read 2026-10-23
  • CNAweakness (CWE)CWE-266, CWE-270known since 2026-10-23
  • NVDweakness (CWE)CWE-269read 2026-10-23
  • FIRST EPSSEPSS score1.1 %2026-11-18
  • OSVaffected packages—
  • GitHub Advisoriesadvisory—

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2020-01-07
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-37jw-xgjq-3fmq

Frequently asked questions

What is CVE-2019-14819?

A flaw was found during the upgrade of an existing OpenShift Container Platform 3.x cluster. Using CRI-O, the dockergc service account is assigned to the current namespace of the user performing the upgrade. This flaw can allow an unprivileged user to escalate their privileges to those allowed by the privileged Security Context Constraints.

Is CVE-2019-14819 actively exploited?

Active exploitation of CVE-2019-14819 has not been confirmed. Its EPSS score was 1.1% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2019-14819?

CVE-2019-14819 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running openshift-ansible? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record