# GHSA-85rg-8m6h-825p: Vulnerabilities with the k8sGPT

> Multiple vulnerabilities were identified in the k8sGPT tool, requiring users to upgrade to the latest release to mitigate potential risks.

- **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:** 13 Jun 2024
- **Also known as:** GO-2024-2923

## What is GHSA-85rg-8m6h-825p?

GHSA-85rg-8m6h-825p is a vulnerability in github.com/k8sgpt-ai/k8sgpt, published on 13 Jun 2024. 

### Official description

### Summary
Bunch of vulnerabilities found in k8sGPT.  Fixed in release https://github.com/k8sgpt-ai/k8sgpt/releases/tag/v0.3.33

## Which versions are affected by GHSA-85rg-8m6h-825p?

3 open source packages ship an affected version, including github.com/k8sgpt-ai/k8sgpt.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/k8sgpt-ai/k8sgpt` | Go | All versions | 0.3.33 |
| `github.com/k8sgpt-ai/k8sgpt` | Go | All versions | 0.3.33 |
| `github.com/k8sgpt-ai/k8sgpt` | Go | All versions | 0.3.33 |

## How do I fix GHSA-85rg-8m6h-825p?

Upgrade github.com/k8sgpt-ai/k8sgpt to 0.3.33 or later.

## Is GHSA-85rg-8m6h-825p being exploited?

There is no known exploitation of GHSA-85rg-8m6h-825p in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-85rg-8m6h-825p and fix it if it is affected.

What it is: GHSA-85rg-8m6h-825p is a vulnerability in github.com/k8sgpt-ai/k8sgpt, published on 13 Jun 2024. 
Exploitation: There is no known exploitation of GHSA-85rg-8m6h-825p in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/k8sgpt-ai/k8sgpt (Go): affected all versions; fixed in 0.3.33
- github.com/k8sgpt-ai/k8sgpt (Go): affected all versions; fixed in 0.3.33
- github.com/k8sgpt-ai/k8sgpt (Go): affected all versions; fixed in 0.3.33

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/GHSA-85rg-8m6h-825p/ (Markdown: https://insights.sbomify.com/GHSA-85rg-8m6h-825p/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-85rg-8m6h-825p

---
From sbomify Insights: https://insights.sbomify.com/GHSA-85rg-8m6h-825p/
Summaries are generated and may contain mistakes; the official description above is the record.