cve.bz

CVE-2019-14819 redhat openshift container platform: Incorrect Privilege Assignment

8.8 highExploit referenceEPSS 1.1%

High (8.8) in redhat openshift container platform. EPSS 1.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
1.1% (unchanged from 1.1% a week ago; 1.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 66th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-266 Incorrect Privilege Assignment
CWE-270 Privilege Context Switching Error
CWE-269 Improper Privilege Management
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2019-14819 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-14819?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-14819?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2019-14819 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
redhat:openshift_container_platform3.10
redhat:openshift_container_platform3.11

Linux distributions

DistributionReleasePackageFixed inAdvisory
Red Hatopenshift:3.11::el7openshift-ansible, openshift-ansible-docs, openshift-ansible-test and 2 more0:3.11.146-1.git.0.fcedb45.el7RHSA-2019:2818

From the distributions' data via OSV.dev: Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Red Hat.

Red Hat

Red Hat rates this Important.

Red Hat's statement

If an upgrade was run with the openshift_crio_enable_docker_gc ansible variable set to 'False' the cluster won't be affected. The default for the variable was set to 'True' before openshift-ansible-3.11.0-0.28.0, and after 3.10.x. See https://github.com/openshift/openshift-ansible/commit/bf5fbea4138f27313c5e4dcd683821975db8e443

Red Hat's mitigation

Make sure your kubeconfig (~/.kube/config) is using the 'default' context when executing, or re-executing a cluster upgrade or install using the ansible playbooks.

ProductPackageStateAdvisory
Red Hat OpenShift Container Platform 3.11openshift-ansible-0:3.11.146-1.git.0.fcedb45.el7Fixed 2019-09-23RHSA-2019:2818
Red Hat OpenShift Container Platform 3.10openshift-ansibleAffected
Red Hat OpenShift Container Platform 3.9openshift-ansibleNot affected
Red Hat OpenShift Container Platform 4openshift-ansibleNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2019-14819.

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-30 Hijacking a Privileged Thread of Execution Likelihood: Low · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-58 Restful Privilege Elevation Likelihood: High · Severity: High
  • CAPEC-122 Privilege Abuse Likelihood: High · Severity: Medium
  • CAPEC-233 Privilege Escalation

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON