# ALBA-2022:2138: rhel-system-roles bug fix and enhancement update

> Bug fixes for Tlog session recording and FIPS mode detection in RHEL system roles for AlmaLinux.

- **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:** 10 May 2022

## What is ALBA-2022:2138?

ALBA-2022:2138 is a vulnerability in rhel-system-roles, published on 10 May 2022. 

### Official description

The rhel-system-roles package includes a collection of Ansible roles and modules that provide a stable and consistent configuration interface for managing multiple versions of AlmaLinux.

Bug Fix(es) and Enhancement(s):

* Tlog role - Enabling session recording configuration does not work due to RHEL9 SSSD files provider default. (BZ#2074653)

* FIPS mode detection in SSHD role is wrong. (BZ#2075536)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rhel-system-roles` | AlmaLinux:8 | All versions | 1.16.2-1.el8 |

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

Apply the vendor's patch.

## Is ALBA-2022:2138 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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