Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/vulndb: potential Go vuln in github.com/helm/helm: CVE-2024-25620 #2554

Closed
GoVulnBot opened this issue Feb 15, 2024 · 1 comment
Closed
Assignees

Comments

@GoVulnBot
Copy link

CVE-2024-25620 references github.com/helm/helm, which may be a Go module.

Description:
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.

References:

Cross references:
No existing reports found with this module or alias.

See doc/triage.md for instructions on how to triage this report.

id: GO-ID-PENDING
modules:
    - module: github.com/helm/helm
      vulnerable_at: 2.17.0+incompatible
      packages:
        - package: helm
cves:
    - CVE-2024-25620
references:
    - advisory: https://github.com/helm/helm/security/advisories/GHSA-v53g-5gjp-272r
    - fix: https://github.com/helm/helm/commit/0d0f91d1ce277b2c8766cdc4c7aa04dbafbf2503

@neild neild self-assigned this Feb 28, 2024
@gopherbot
Copy link
Contributor

Change https://go.dev/cl/568035 mentions this issue: data/reports: add GO-2024-2554.yaml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants