# SUSE-SU-2023:1901-1: Security update for helm

> Security update for Helm package manager addressing dependency and build issues, relevant for developers using Helm.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 18 Apr 2023

## What is SUSE-SU-2023:1901-1?

SUSE-SU-2023:1901-1 is a vulnerability in helm, published on 18 Apr 2023. 

### Official description

This update for helm fixes the following issues:

Update to version 3.11.2:

* chore(deps): bump github.com/rubenv/sql-migrate from 1.2.0 to 1.3.1
* the linter varcheck and deadcode are deprecated (since v1.49.0)
* fix template --output-dir issue
* build against a supported go version: go1.19 (bsc#1209670)

## Which versions are affected by SUSE-SU-2023:1901-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `helm` | SUSE:Linux Enterprise Module for Containers 15 SP4 | All versions | 3.11.2-150000.1.19.1 |
| `helm` | SUSE:Linux Enterprise Module for Package Hub 15 SP4 | All versions | 3.11.2-150000.1.19.1 |
| `helm` | openSUSE:Leap 15.4 | All versions | 3.11.2-150000.1.19.1 |

## How do I fix SUSE-SU-2023:1901-1?

Upgrade to a fixed version.

## Is SUSE-SU-2023:1901-1 being exploited?

There is no known exploitation of SUSE-SU-2023:1901-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2023:1901-1 and fix it if it is affected.

What it is: SUSE-SU-2023:1901-1 is a vulnerability in helm, published on 18 Apr 2023. 
Exploitation: There is no known exploitation of SUSE-SU-2023:1901-1 in the wild and no public exploit code.

Affected product: helm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/SUSE-SU-2023-1901-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2023-1901-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2023:1901-1

---
From sbomify Insights: https://insights.sbomify.com/SUSE-SU-2023-1901-1/
Summaries are generated and may contain mistakes; the official description above is the record.