helm.sh/helm/v3-v3.10.3: 3 vulnerabilities (highest severity is: 7.5)

[mend-bolt-for-github]

Vulnerable Library - helm.sh/helm/v3-v3.10.3

Library home page: https://proxy.golang.org/helm.sh/helm/v3/@v/v3.10.3.zip

Path to dependency file: /capten/go.mod

Path to vulnerable library: /go/pkg/mod/cache/download/helm.sh/helm/v3/@v/v3.10.3.mod

Found in HEAD commit: ef6d2d14ba20ad161dda103d1ac6ed92c19687bb

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in (helm.sh/helm/v3-v3.10.3 version)	Remediation Possible**
CVE-2024-26147	High	7.5	helm.sh/helm/v3-v3.10.3	Direct	v3.14.2	❌
CVE-2024-25620	Medium	6.4	helm.sh/helm/v3-v3.10.3	Direct	v3.14.1	❌
CVE-2023-25173	Medium	5.3	github.com/Containerd/Containerd-v1.6.15	Transitive	N/A*	❌

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2024-26147

Vulnerable Library - helm.sh/helm/v3-v3.10.3

Library home page: https://proxy.golang.org/helm.sh/helm/v3/@v/v3.10.3.zip

Path to dependency file: /capten/go.mod

Path to vulnerable library: /go/pkg/mod/cache/download/helm.sh/helm/v3/@v/v3.10.3.mod

Dependency Hierarchy:

• ❌ helm.sh/helm/v3-v3.10.3 (Vulnerable Library)

Found in HEAD commit: ef6d2d14ba20ad161dda103d1ac6ed92c19687bb

Found in base branch: main

Vulnerability Details

Helm is a package manager for Charts for Kubernetes. Versions prior to 3.14.2 contain an 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.

Publish Date: 2024-02-21

URL: CVE-2024-26147

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-r53h-jv2g-vpx6

Release Date: 2024-02-21

Fix Resolution: v3.14.2

Step up your Open Source Security Game with Mend here

CVE-2024-25620

Vulnerable Library - helm.sh/helm/v3-v3.10.3

Library home page: https://proxy.golang.org/helm.sh/helm/v3/@v/v3.10.3.zip

Path to dependency file: /capten/go.mod

Path to vulnerable library: /go/pkg/mod/cache/download/helm.sh/helm/v3/@v/v3.10.3.mod

Dependency Hierarchy:

• ❌ helm.sh/helm/v3-v3.10.3 (Vulnerable Library)

Found in HEAD commit: ef6d2d14ba20ad161dda103d1ac6ed92c19687bb

Found in base branch: main

Vulnerability Details

Helm is a tool for managing Charts. Charts are packages of pre-configured Kubernetes resources. When either the Helm client or SDK is used to save a chart whose name within the Chart.yaml file includes a relative path change, the chart would be saved outside its expected directory based on the changes in the relative path. The validation and linting did not detect the path changes in the name. This issue has been resolved in Helm v3.14.1. Users unable to upgrade should check all charts used by Helm for path changes in their name as found in the Chart.yaml file. This includes dependencies.

Publish Date: 2024-02-14

URL: CVE-2024-25620

CVSS 3 Score Details (6.4)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: Low
  • User Interaction: None
  • Scope: Changed
• Impact Metrics:
  • Confidentiality Impact: Low
  • Integrity Impact: Low
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://www.cve.org/CVERecord?id=CVE-2024-25620

Release Date: 2024-02-14

Fix Resolution: v3.14.1

Step up your Open Source Security Game with Mend here

CVE-2023-25173

Vulnerable Library - github.com/Containerd/Containerd-v1.6.15

Library home page: https://proxy.golang.org/github.com/!containerd/!containerd/@v/v1.6.15.zip

Path to dependency file: /capten/go.mod

Path to vulnerable library: /go/pkg/mod/cache/download/github.com/containerd/containerd/@v/v1.6.15.mod

Dependency Hierarchy:

• helm.sh/helm/v3-v3.10.3 (Root Library)
  • ❌ github.com/Containerd/Containerd-v1.6.15 (Vulnerable Library)

Found in HEAD commit: ef6d2d14ba20ad161dda103d1ac6ed92c19687bb

Found in base branch: main

Vulnerability Details

containerd is an open source container runtime. A bug was found in containerd prior to versions 1.6.18 and 1.5.18 where supplementary groups are not set up properly inside a container. If an attacker has direct access to a container and manipulates their supplementary group access, they may be able to use supplementary group access to bypass primary group restrictions in some cases, potentially gaining access to sensitive information or gaining the ability to execute code in that container. Downstream applications that use the containerd client library may be affected as well.

This bug has been fixed in containerd v1.6.18 and v.1.5.18. Users should update to these versions and recreate containers to resolve this issue. Users who rely on a downstream application that uses containerd's client library should check that application for a separate advisory and instructions. As a workaround, ensure that the "USER $USERNAME" Dockerfile instruction is not used. Instead, set the container entrypoint to a value similar to ENTRYPOINT ["su", "-", "user"] to allow su to properly set up supplementary groups.

Publish Date: 2023-02-16

URL: CVE-2023-25173

CVSS 3 Score Details (5.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Local
  • Attack Complexity: Low
  • Privileges Required: Low
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: Low
  • Integrity Impact: Low
  • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-hmfx-3pcx-653p

Release Date: 2023-02-16

Fix Resolution: v1.5.18,v1.6.18

Step up your Open Source Security Game with Mend here

[mend-bolt-for-github]

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[mend-bolt-for-github]

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.

[mend-bolt-for-github]

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[mend-bolt-for-github]

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.

[mend-bolt-for-github]

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[mend-bolt-for-github]

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.