← Back
CVE-2024-7387
critical
CVSS 9.1
Vulnerability in github.com/openshift/builder (CVE-2024-7387)
Summary
vulnerability in github.com/openshift/builder (CVE-2024-7387). Successful exploitation can lead to full system takeover. Exploitable via ``spec.source.secrets.secret.destinationDir``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-7387** has been found in github.com/openshift/builder.
Attackers can target a specific entry point like ``spec.source.secrets.secret.destinationDir`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "github.com/openshift/builder CVE-2024-7387" on the vendor's site.
CVE-2024-7387 (github.com/openshift/builder) — CWE-250 / CVSS v3 9.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `spec.source.secrets.secret.destinationDir` / `BuildConfig`
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-250) exists in github.com/openshift/builder. Attackers reach the vulnerable code path via ``spec.source.secrets.secret.destinationDir`` without authentication.
📍 Affected scope
github.com/openshift/builder — . Attack surface: `spec.source.secrets.secret.destinationDir` / `BuildConfig`.
🔥 Severity
Severity: Critical (CVSS 9.1/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/openshift/builder' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/openshift/builder' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/openshift/builder` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/openshift/builder
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
References
- web https://access.redhat.com/errata/RHSA-2024:3718
- web https://access.redhat.com/errata/RHSA-2024:6122
- web https://access.redhat.com/errata/RHSA-2024:6685
- web https://access.redhat.com/errata/RHSA-2024:6687
- web https://access.redhat.com/errata/RHSA-2024:6689
- web https://access.redhat.com/errata/RHSA-2024:6691
- web https://access.redhat.com/errata/RHSA-2024:6705
- web https://access.redhat.com/security/cve/CVE-2024-7387
- web https://bugzilla.redhat.com/show_bug.cgi?id=2302259
- web https://github.com/openshift/builder/commit/0b62633adfa2836465202bc851885e078ec888d1
- web https://stuxxn.github.io/advisory/2024/10/02/openshift-build-docker-priv-esc.html
- web https://nvd.nist.gov/vuln/detail/CVE-2024-7387
- web https://pkg.go.dev/vuln/GO-2024-3129
- web https://github.com/advisories/GHSA-qqv8-ph7f-h3f7