# ALBA-2021:3661: container-tools:rhel8 bug fix update

> An update fixes a bug where kubelet fails to load environment files due to SELinux denials in container tools.

- **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:** 23 Sep 2021

## What is ALBA-2021:3661?

ALBA-2021:3661 is a vulnerability in containernetworking-plugins, published on 23 Sep 2021. 

### Official description

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

Bug Fix:

* kubelet service fail to load EnvironmentFile due to SELinux denial (BZ#2005053)

## Which versions are affected by ALBA-2021:3661?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `containernetworking-plugins` | AlmaLinux:8 | All versions | 0.9.1-1.module_el8.6.0+2876+9ed4eae2 |
| `crit` | AlmaLinux:8 | All versions | 3.15-1.module_el8.6.0+2876+9ed4eae2 |
| `criu` | AlmaLinux:8 | All versions | 3.15-1.module_el8.6.0+2876+9ed4eae2 |
| `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 |
| `python3-criu` | AlmaLinux:8 | All versions | 3.15-1.module_el8.6.0+2876+9ed4eae2 |
| `slirp4netns` | AlmaLinux:8 | All versions | 1.1.8-1.module_el8.6.0+2876+9ed4eae2 |

## How do I fix ALBA-2021:3661?

Apply the vendor's patch.

## Is ALBA-2021:3661 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2021:3661 is a vulnerability in containernetworking-plugins, published on 23 Sep 2021. 
Exploitation: There is no known exploitation of ALBA-2021:3661 in the wild and no public exploit code.

Affected product: containernetworking-plugins. 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-2021-3661/ (Markdown: https://insights.sbomify.com/ALBA-2021-3661/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2021:3661

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