Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2020-15187

Vulnerability in helm.sh/helm/v3 (CVE-2020-15187)

Summary

Vulnerability in helm.sh/helm/v3 (CVE-2020-15187). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.3.2 or later.

Original description

The description as published by the source.

In Helm before versions 2.16.11 and 3.3.2, a Helm plugin can contain duplicates of the same entry, with the last one always used. If a plugin is compromised, this lowers the level of access that an attacker needs to modify a plugin's install hooks, causing a local execution attack.
To perform this attack, an attacker must have write access to the git repository or plugin archive (.tgz) while being downloaded (which can occur during a MITM attack on a non-SSL connection). This issue has been patched in Helm 2.16.11 and Helm 3.3.2.
As a possible workaround make sure to install plugins using a secure connection protocol like SSL.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2020-15187 has been found in helm.sh/helm/v3.
Risk of unauthorized operations or information disclosure.
What to do: upgrade helm.sh/helm/v3 to 3.3.2 or later.
If unsure, ask your IT team or search "helm.sh/helm/v3 CVE-2020-15187" on the vendor's site.

CVE-2020-15187 (helm.sh/helm/v3) — CWE-694
Attack vector: remote (network-reachable)
Patched: 3.3.2 — apply immediately
Workaround: Make sure to install plugins using a secure connection protocol like SSL.
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-694) exists in helm.sh/helm/v3.

📍 Affected scope

Check the vendor advisory for the affected versions of helm.sh/helm/v3.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.3.2.

🛡️ Workaround

Workaround: Make sure to install plugins using a secure connection protocol like SSL.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'helm.sh/helm/v3' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'helm.sh/helm/v3' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で helm.sh/helm/v3 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Make sure to install plugins using a secure connection protocol like SSL.

    パッチが適用されるまでの応急処置として、Make sure to install plugins using a secure connection protocol like SSL. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade helm.sh/helm/v3 to 3.3.2

    ステージング環境で 3.3.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go helm.sh/helm/v3
[{"type":"SEMVER","events":[{"introduced":"3.0.0"},{"fixed":"3.3.2"}]}]
Go helm.sh/helm
[{"type":"SEMVER","events":[{"introduced":"2.0.0"},{"fixed":"2.16.11"}]}]
Bitnami helm
[{"type":"SEMVER","events":[{"introduced":"2.0.0"},{"fixed":"2.16.11"},{"introduced":"3.0.0"},{"fixed":"3.3.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details