Skip to content
VulniPulse
Advisory severityCritical9.1Vendor: HighRed Hat Linux

Critical [CVE-2024-7387] Openshift/builder: path traversal allows command injection in privileged buildcontainer using docker build strategy

This critical-severity Red Hat Linux advisory covers CVE-2024-7387 affecting Red Hat OpenShift Container Platform 4.12, Red Hat OpenShift Container Platform 4.13, Red Hat OpenShift Container Platform 4.14.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2024-7387 Source published Source updated

VulniPulse record published

CVE-2024-7387
Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Summary

A flaw was found in openshift/builder. When using the “Docker” strategy, executable files inside the privileged build container can be overridden using the `spec.source.secrets.secret.destinationDir` attribute of the `BuildConfig` definition.

An attacker running code in a privileged container could escalate their permissions on the node running the container. In all versions of OpenShift, the "Custom" build strategy gives developers permission to run arbitrary commands in a privileged container.

This is disabled by default, and documentation explicitly warns that this should only be enabled for highly trusted users (eg: cluster admins). We therefore do not consider this vulnerability a privilege escalation path for "Custom" strategy builds.

Microshift is not affected by this vulnerability. Red Hat severity: Important — CVSS 9.1 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Weakness: CWE-250. Affected Red Hat products: Red Hat OpenShift Container Platform 4.12; Red Hat OpenShift Container Platform 4.13; Red Hat OpenShift Container Platform 4.14; Red Hat OpenShift Container Platform 4.15; Red Hat OpenShift Container Platform 4.16; Red Hat OpenShift Container Platform 4.17; Red Hat OpenShift Container Platform 4.18.

Red Hat fixing advisory: RHSA-2024:6705, RHSA-2024:6691, RHSA-2024:6689, RHSA-2024:6685, RHSA-2024:6687, RHSA-2024:3718, RHSA-2024:6122.

Is CVE-2024-7387 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2024-7387 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2024-7387?

Upgrade to a fixed release named by Red Hat:

  • openshift4/ose-docker-builder:v4.12.0-202409121032.p1.g609473f.assembly.stream.el8
  • openshift4/ose-docker-builder:v4.13.0-202409120505.p1.g2c7e99d.assembly.stream.el8
  • openshift4/ose-docker-builder:v4.14.0-202409111409.p1.g52565ca.assembly.stream.el8
  • openshift4/ose-docker-builder:v4.15.0-202409101936.p1.ge7749a3.assembly.stream.el8
  • openshift4/ose-docker-builder-rhel9:v4.16.0-202409101737.p1.gfee4b58.assembly.stream.el9
  • openshift4/ose-docker-builder-rhel9:v4.17.0-202409122005.p1.gcfcf3bd.assembly.stream.el9
  • openshift4/aws-kms-encryption-provider-rhel9:v4.18.0-202501230001.p0.g088dcaf.assembly.stream.el9
  • openshift4/azure-kms-encryption-provider-rhel9:v4.18.0-202501230001.p0.gd4fb1b6.assembly.stream.el9
  • openshift4/azure-service-rhel9-operator:v4.18.0-202501230001.p0.g11ced00.assembly.stream.el9
  • openshift4/cloud-network-config-controller-rhel9:v4.18.0-202501230001.p0.gf648c78.assembly.stream.el9
  • openshift4/container-networking-plugins-microshift-rhel9:v4.18.0-202501230001.p0.g24a6532.assembly.stream.el9
  • openshift4/driver-toolkit-rhel9:v4.18.0-202502100301.p0.g2e139ed.assembly.stream.el9

35 more fixed releases are listed below.

Confirm against the vendor advisory before you patch.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.

Official advisory · high-confidence parse· fetched 19 days ago·verify at source

Fixed versions
  • openshift4/ose-docker-builder:v4.12.0-202409121032.p1.g609473f.assembly.stream.el8
  • openshift4/ose-docker-builder:v4.13.0-202409120505.p1.g2c7e99d.assembly.stream.el8
  • openshift4/ose-docker-builder:v4.14.0-202409111409.p1.g52565ca.assembly.stream.el8
  • openshift4/ose-docker-builder:v4.15.0-202409101936.p1.ge7749a3.assembly.stream.el8
  • openshift4/ose-docker-builder-rhel9:v4.16.0-202409101737.p1.gfee4b58.assembly.stream.el9
  • openshift4/ose-docker-builder-rhel9:v4.17.0-202409122005.p1.gcfcf3bd.assembly.stream.el9
  • openshift4/aws-kms-encryption-provider-rhel9:v4.18.0-202501230001.p0.g088dcaf.assembly.stream.el9
  • openshift4/azure-kms-encryption-provider-rhel9:v4.18.0-202501230001.p0.gd4fb1b6.assembly.stream.el9
  • openshift4/azure-service-rhel9-operator:v4.18.0-202501230001.p0.g11ced00.assembly.stream.el9
  • openshift4/cloud-network-config-controller-rhel9:v4.18.0-202501230001.p0.gf648c78.assembly.stream.el9
  • openshift4/container-networking-plugins-microshift-rhel9:v4.18.0-202501230001.p0.g24a6532.assembly.stream.el9
  • openshift4/driver-toolkit-rhel9:v4.18.0-202502100301.p0.g2e139ed.assembly.stream.el9
  • openshift4/egress-router-cni-rhel9:v4.18.0-202501230001.p0.g3193a75.assembly.stream.el9
  • openshift4/frr-rhel9:v4.18.0-202502041302.p0.g1ad8f2e.assembly.stream.el9
  • openshift4/insights-runtime-exporter-rhel9:v4.18.0-202501230001.p0.g7149f2d.assembly.stream.el9
  • openshift4/insights-runtime-extractor-rhel9:v4.18.0-202501230001.p0.g7149f2d.assembly.stream.el9
  • openshift4/kube-metrics-server-rhel9:v4.18.0-202501230001.p0.g962ccca.assembly.stream.el9
  • openshift4/kubevirt-csi-driver-rhel9:v4.18.0-202501230001.p0.gba2234b.assembly.stream.el9
  • openshift4/network-tools-rhel9:v4.18.0-202502111035.p0.gf76635f.assembly.stream.el9
  • openshift4/oc-mirror-plugin-rhel9:v4.18.0-202502100934.p0.gc00c7c9.assembly.stream.el9
  • openshift4/openshift-route-controller-manager-rhel9:v4.18.0-202501230001.p0.g07daee4.assembly.stream.el9
  • openshift4/ose-agent-installer-api-server-rhel9:v4.18.0-202502040032.p0.ge5a4005.assembly.stream.el9
  • openshift4/ose-agent-installer-csr-approver-rhel9:v4.18.0-202502040032.p0.g5348c85.assembly.stream.el9
  • openshift4/ose-agent-installer-node-agent-rhel9:v4.18.0-202502041302.p0.g51a74ac.assembly.stream.el9
  • openshift4/ose-agent-installer-orchestrator-rhel9:v4.18.0-202501230001.p0.g5348c85.assembly.stream.el9
  • openshift4/ose-agent-installer-utils-rhel9:v4.18.0-202501230001.p0.g3f6d1d8.assembly.stream.el9
  • openshift4/ose-apiserver-network-proxy-rhel9:v4.18.0-202501230001.p0.g0e11616.assembly.stream.el9
  • openshift4/ose-aws-cloud-controller-manager-rhel9:v4.18.0-202501230001.p0.gc395190.assembly.stream.el9
  • openshift4/ose-aws-cluster-api-controllers-rhel9:v4.18.0-202501230001.p0.g6bd77fc.assembly.stream.el9
  • openshift4/ose-aws-ebs-csi-driver-rhel9:v4.18.0-202501230001.p0.gb51cd6b.assembly.stream.el9
  • openshift4/ose-aws-ebs-csi-driver-rhel9-operator:v4.18.0-202501230001.p0.g9432fd3.assembly.stream.el9
  • openshift4/ose-aws-pod-identity-webhook-rhel9:v4.18.0-202501230001.p0.g5c43fe8.assembly.stream.el9
  • openshift4/ose-azure-cloud-controller-manager-rhel9:v4.18.0-202501230001.p0.g9c24d76.assembly.stream.el9
  • openshift4/ose-azure-cloud-node-manager-rhel9:v4.18.0-202501230001.p0.g9c24d76.assembly.stream.el9
  • openshift4/ose-azure-cluster-api-controllers-rhel9:v4.18.0-202501230001.p0.g987615c.assembly.stream.el9
  • openshift4/ose-azure-disk-csi-driver-rhel9:v4.18.0-202501241902.p0.g6cced66.assembly.stream.el9
  • openshift4/ose-azure-disk-csi-driver-rhel9-operator:v4.18.0-202501230001.p0.g9432fd3.assembly.stream.el9
  • openshift4/ose-azure-file-csi-driver-operator-rhel9:v4.18.0-202501230001.p0.g9432fd3.assembly.stream.el9
  • openshift4/ose-azure-file-csi-driver-rhel9:v4.18.0-202501230001.p0.g4b34592.assembly.stream.el9
  • openshift4/ose-azure-workload-identity-webhook-rhel9:v4.18.0-202501230001.p0.g344c5dc.assembly.stream.el9
  • RHSA-2024:6705
  • RHSA-2024:6691
  • RHSA-2024:6689
  • RHSA-2024:6685
  • RHSA-2024:6687
  • RHSA-2024:3718
  • RHSA-2024:6122

Official advisory · high-confidence parse· fetched 19 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Cluster admins can follow the instructions in "Securing Builds by Strategy" to block use of the "Docker" build strategy on a cluster, or restrict the use to a set of highly trusted users, until the cluster is able to be upgraded. https://docs.openshift.com/container-platform/4.16/cicd/builds/securing-builds-by-strategy.html

Official advisory · high-confidence parse· fetched 19 days ago·verify at source

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat
All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.