# ALBA-2022:2145: osbuild-composer bug fix and enhancement update


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 10 May 2022

## What is ALBA-2022:2145?

ALBA-2022:2145 is a vulnerability in osbuild-composer, published on 10 May 2022. 

### Official description

The osbuild-composer package is a service for building customized OS artifacts, such as virtual machine (VM) images and OSTree commits. Apart from building images for local usage, it can also upload images directly to cloud. The package is compatible with composer-cli and cockpit-composer clients.

Bug Fix(es) and Enhancement(s):

* Building AlmaLinux 8.6 with filesystem customizations will lead to incorrect LVM layout. (BZ#2079804)

## Which versions are affected by ALBA-2022:2145?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `osbuild-composer` | AlmaLinux:8 | All versions | 46.3-1.el8_6 |
| `osbuild-composer-core` | AlmaLinux:8 | All versions | 46.3-1.el8_6 |
| `osbuild-composer-dnf-json` | AlmaLinux:8 | All versions | 46.3-1.el8_6 |
| `osbuild-composer-worker` | AlmaLinux:8 | All versions | 46.3-1.el8_6 |

## How do I fix ALBA-2022:2145?

Upgrade to a fixed version.

## Is ALBA-2022:2145 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2022:2145 is a vulnerability in osbuild-composer, published on 10 May 2022. 
Exploitation: There is no known exploitation of ALBA-2022:2145 in the wild and no public exploit code.

Affected product: osbuild-composer. 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-2022-2145/ (Markdown: https://insights.sbomify.com/ALBA-2022-2145/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2022:2145

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