# ALBA-2020:5496: container-tools:rhel8 bug fix update

> This is a bug fix update for container tools, not a security vulnerability, so no specific attack vector or impact is described.

- **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:** 15 Dec 2020

## What is ALBA-2020:5496?

ALBA-2020:5496 is a vulnerability in libslirp, published on 15 Dec 2020. 

### Official description

The container-tools module contains tools for working with containers, notably podman, buildah, skopeo, and runc.

Bug Fix(es):

* update description and summary for container-tools module for 8.3.0 (BZ#1898204)

## Which versions are affected by ALBA-2020:5496?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libslirp` | AlmaLinux:8 | All versions | 4.3.1-1.module_el8.6.0+2876+9ed4eae2 |
| `libslirp-devel` | AlmaLinux:8 | All versions | 4.3.1-1.module_el8.6.0+2876+9ed4eae2 |
| `python-podman-api` | AlmaLinux:8 | All versions | 1.2.0-0.2.gitd0a45fe.module_el8.5.0+108+00865455 |
| `python-podman-api` | AlmaLinux:8 | All versions | 1.2.0-0.2.gitd0a45fe.module_el8.5.0+2635+e4386a39 |

## How do I fix ALBA-2020:5496?

Upgrade to a fixed version.

## Is ALBA-2020:5496 being exploited?

There is no known exploitation of ALBA-2020:5496 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for ALBA-2020:5496 and fix it if it is affected.

What it is: ALBA-2020:5496 is a vulnerability in libslirp, published on 15 Dec 2020. 
Exploitation: There is no known exploitation of ALBA-2020:5496 in the wild and no public exploit code.

Affected product: libslirp. 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/ALBA-2020-5496/ (Markdown: https://insights.sbomify.com/ALBA-2020-5496/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2020:5496

---
From sbomify Insights: https://insights.sbomify.com/ALBA-2020-5496/
Summaries are generated and may contain mistakes; the official description above is the record.