Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-qqv8-ph7f-h3f7

CRITICALFix: openshift/builder@0b62633

GHSA-qqv8-ph7f-h3f7 is a critical-severity (CVSS 9.1) CWE-250 vulnerability in github.com/openshift/builder. O3 Security confirms whether GHSA-qqv8-ph7f-h3f7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenShift Builder has a path traversal, allows command injection in privileged BuildContainer

Also known asCVE-2024-7387GO-2024-3129
Published
Sep 17, 2024
Updated
Jan 9, 2025
Affected
1 pkg
Patched
None yet
Exploits
None indexed

Real-World Exposure

1 pkg affected
🐹github.com/openshift/builder

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

A flaw was found in openshift/builder. This vulnerability allows command injection via path traversal, where a malicious user can execute arbitrary commands on the OpenShift node running the builder container. 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.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/openshift/builderall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/openshift/builder. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of github.com/openshift/builder has shipped for GHSA-qqv8-ph7f-h3f7 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-qqv8-ph7f-h3f7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-qqv8-ph7f-h3f7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A flaw was found in openshift/builder. This vulnerability allows command injection via path traversal, where a malicious user can execute arbitrary commands on the OpenShift node running the builder container. 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.
O3 Security · Impact-Aware SCA

Is GHSA-qqv8-ph7f-h3f7 in your dependencies?

O3 detects GHSA-qqv8-ph7f-h3f7 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.