LiveActive security incident?Get immediate response
CVE Record

CVE-2020-15187: Duplicate plugin entries in Helm

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.

LowCVSS 3Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a low-severity Helm plugin handling flaw. A tampered plugin could use duplicate metadata entries so Helm uses the last entry, making it easier to alter install hooks and trigger local code execution during plugin installation.

Executive priority

Treat this as hygiene-level risk unless Helm plugin installation is common in CI or sensitive build environments. Prioritize upgrades during normal maintenance, with faster action where plugins are fetched from external sources.

Technical view

Helm before 2.16.11 and 3.3.2 accepted duplicate plugin entries and used the final duplicate. The advisory says this can lower the access needed to modify plugin install hooks when a plugin repository or archive is compromised during download.

Likely exposure

Exposure is mainly developer workstations, CI runners, and build systems using Helm 2.x before 2.16.11 or Helm 3.x before 3.3.2 that install plugins from untrusted or non-SSL sources.

Exploitation context

Sources do not report active exploitation, and KEV is false. Attack requires user interaction and attacker control over a plugin git repository, plugin archive, or non-SSL download path.

Researcher notes

The core issue is parser behavior around duplicate plugin entries. The public record identifies affected versions, patched versions, prerequisites, and SSL as a workaround, but does not provide evidence of exploitation in the wild.

Mitigation direction

  • Upgrade Helm 2.x to 2.16.11 or later.
  • Upgrade Helm 3.x to 3.3.2 or later.
  • Install Helm plugins only over secure SSL connections.
  • Check Helm vendor guidance before accepting third-party plugin workarounds.
  • Prefer trusted plugin sources in developer and CI workflows.

Validation and detection

  • Inventory Helm versions on workstations, CI runners, and build images.
  • Identify Helm plugin installation workflows and their source URLs.
  • Flag plugin installs that use non-SSL transport.
  • Review installed plugins for unexpected install hooks or duplicate metadata entries.
  • Confirm patched Helm versions reject unsafe duplicate plugin entries.
Prepared
Confidence
high
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-694: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-74: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-15187 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
8Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
3CVSS 3.1LowCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:N1.31.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3Low
CVSS 3.1 vector shape for CVE-2020-15187Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
helmhelm>= 2.0.0, < 2.16.11, >= 3.0.0, < 3.3.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-694 · source CWE mapping

Use of Multiple Resources with Duplicate Identifier

Use of Multiple Resources with Duplicate Identifier represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-74 · source CWE mapping

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.