# ALBA-2019:0973: container-tools bug fix update

> An update for container-tools fixes several bugs, requiring users to upgrade to ensure stability and security.

- **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:** 7 May 2019

## What is ALBA-2019:0973?

ALBA-2019:0973 is a vulnerability in oci-systemd-hook, published on 7 May 2019. 

### Official description

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

Users of container-tools are advised to upgrade to this updated package, which fixes several bugs.

## Which versions are affected by ALBA-2019:0973?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `oci-systemd-hook` | AlmaLinux:8 | All versions | 1:0.1.15-2.git2d0b8a3.module_el8.3.0+2044+12421f43 |
| `oci-systemd-hook` | AlmaLinux:8 | All versions | 1:0.1.15-2.git2d0b8a3.module_el8.4.0+2496+12421f43 |
| `oci-systemd-hook` | AlmaLinux:8 | All versions | 1:0.1.15-2.git2d0b8a3.module_el8.5.0+119+9a9ec082 |
| `oci-umount` | AlmaLinux:8 | All versions | 2:2.3.4-2.git87f9237.module_el8.3.0+2044+12421f43 |
| `oci-umount` | AlmaLinux:8 | All versions | 2:2.3.4-2.git87f9237.module_el8.4.0+2496+12421f43 |
| `oci-umount` | AlmaLinux:8 | All versions | 2:2.3.4-2.git87f9237.module_el8.5.0+119+9a9ec082 |

## How do I fix ALBA-2019:0973?

Upgrade to a fixed version.

## Is ALBA-2019:0973 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2019:0973 is a vulnerability in oci-systemd-hook, published on 7 May 2019. 
Exploitation: There is no known exploitation of ALBA-2019:0973 in the wild and no public exploit code.

Affected product: oci-systemd-hook. 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-2019-0973/ (Markdown: https://insights.sbomify.com/ALBA-2019-0973/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2019:0973

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