# ALBA-2022:0349: clevis bug fix and enhancement update

> Clevis hangs during boot requiring user interaction, causing a denial of service in automated decryption scenarios.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 Feb 2022

## What is ALBA-2022:0349?

ALBA-2022:0349 is a denial of service vulnerability in clevis, published on 1 Feb 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Clevis is a pluggable framework for automated decryption. It can be used to
provide automated decryption of data or even automated unlocking of LUKS
volumes. The clevis packages provide the client side of the Network Bound
Disk Encryption (NBDE) project.

Bug Fix(es) and Enhancement(s):

* Server hangs in asking password unless user hits enter in clevis/dracut
(BZ#2023256)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `clevis` | AlmaLinux:8 | All versions | 15-1.el8_5.1 |
| `clevis-dracut` | AlmaLinux:8 | All versions | 15-1.el8_5.1 |
| `clevis-luks` | AlmaLinux:8 | All versions | 15-1.el8_5.1 |
| `clevis-systemd` | AlmaLinux:8 | All versions | 15-1.el8_5.1 |
| `clevis-udisks2` | AlmaLinux:8 | All versions | 15-1.el8_5.1 |

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

Apply the vendor's patch.

## Is ALBA-2022:0349 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2022:0349 is a denial of service vulnerability in clevis, published on 1 Feb 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of ALBA-2022:0349 in the wild and no public exploit code.

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

## Sources

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

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