A Helm contributor discovered uninitialized variable vulnerability when Helm parses index and plugin yaml files missing expected content.
When either an index.yaml
file or a plugins plugin.yaml
file were missing all metadata a panic would occur in Helm.
In the Helm SDK this is found when using the LoadIndexFile
or DownloadIndexFile
functions in the repo
package or the LoadDir
function in the plugin
package. For the Helm client this impacts functions around adding a repository and all Helm functions if a malicious plugin is added as Helm inspects all known plugins on each invocation.
This issue has been resolved in Helm v3.14.2.
If a malicious plugin has been added which is causing all Helm client commands to panic, the malicious plugin can be manually removed from the filesystem.
If using Helm SDK versions prior to 3.14.2, calls to affected functions can use recover
to catch the panic.
Helm's security policy is spelled out in detail in our SECURITY document.
Disclosed by Jakub Ciolek at AlphaSense.
Use of Uninitialized Variable
Use of Uninitialized Variable
Use of Uninitialized Variable
3.9
Package | Type | OS Name | OS Version | Affected Ranges | Fix Versions |
---|---|---|---|---|---|
helm.sh/helm/v3 | golang | - | - | <3.14.2 | 3.14.2 |
CVSS:3 Severity and metrics
The CVSS metrics represent various qualitative aspects of a vulnerability that influence the overall score above.
Attack Vector (AV)
Network
The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone). One example of an Adjacent attack would be an ARP (IPv4) or neighbor discovery (IPv6) flood leading to a denial of service on the local LAN segment (e.g., CVE-2013-6014).
Attack Complexity (AC)
Low
Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.
Privileges Required (PR)
None
The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction (UI)
None
The vulnerable system can be exploited without interaction from any user.
Scope (S)
Unchanged
An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality (C)
None
There is no loss of confidentiality.
Integrity (I)
None
There is no loss of trust or accuracy within the impacted component.
Availability (A)
High
There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component.
3.9
-
-
BIT-helm-2024-26147
-
3.9
CGA-36wv-76w4-qx9x
-
CGA-2q69-4vcm-hm2w
-
CGA-47c6-49xx-rr4p
-
CGA-3jg2-5m28-f2v4
-
CGA-4v62-mgwp-fff2
-
CGA-6fhm-qph5-fvrj
-
CGA-6qr5-2pq4-4j8h
-
CGA-76fg-85mc-8728
-
CGA-87cp-vv6g-953p
-
CGA-7hpm-5vwh-wpjm
-
CGA-9p49-67j6-3fwx
-
CGA-cffv-prrf-jc52
-
CGA-crc8-wfgr-263v
-
CGA-cx4x-4xcg-64q6
-
CGA-fjmw-2v4h-gmw6
-
CGA-gwcx-28j8-h2f5
-
CGA-gxjr-qgvh-8rp5
-
CGA-p75f-jjr2-x29v
-
CGA-p8m8-xcqf-5mxr
-
CGA-q6xc-h255-cg48
-
CGA-r8j4-mfm2-9m2r
-
CGA-rp6f-6683-234c
-
CGA-w69x-4pr7-3qww
-
CGA-x234-xj6j-25f6
-
CGA-wqx2-j5x2-gmhg
-
CGA-xg36-qjh4-wc7w
-