# SUSE-SU-2024:2639-1: This update for kubevirt, virt-api-container, virt-controller-container, virt-exportproxy-container, virt-exportserver-container, virt-handl


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 30 Jul 2024

## What is SUSE-SU-2024:2639-1?

SUSE-SU-2024:2639-1 is a vulnerability in kubevirt, published on 30 Jul 2024. 

### Official description

This update for kubevirt, virt-api-container, virt-controller-container, virt-exportproxy-container, virt-exportserver-container, virt-handler-container, virt-launcher-container, virt-libguestfs-tools-container, virt-operator-container, virt-pr-helper-container fixes the following issues:

- Update to version 1.2.2

  Release notes https://github.com/kubevirt/kubevirt/releases/tag/v1.2.2
  Release notes https://github.com/kubevirt/kubevirt/releases/tag/v1.2.1
  Release notes https://github.com/kubevirt/kubevirt/releases/tag/v1.2.0

- Use predefined configuration files for libvirt
- Install psmisc (provides killall for tests)

## Which versions are affected by SUSE-SU-2024:2639-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kubevirt` | SUSE:Linux Enterprise Module for Containers 15 SP6 | All versions | 1.2.2-150600.5.6.1 |
| `kubevirt` | openSUSE:Leap 15.6 | All versions | 1.2.2-150600.5.6.1 |

## How do I fix SUSE-SU-2024:2639-1?

Upgrade to a fixed version.

## Is SUSE-SU-2024:2639-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2024:2639-1 is a vulnerability in kubevirt, published on 30 Jul 2024. 
Exploitation: There is no known exploitation of SUSE-SU-2024:2639-1 in the wild and no public exploit code.

Affected product: kubevirt. 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-2024-2639-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2024-2639-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2024:2639-1

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