# ALBA-2022:2139: tlog bug fix and enhancement update

> A bug in tlog caused SSH to fail running commands reliably, potentially disrupting terminal sessions for users on AlmaLinux systems.

- **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:2139?

ALBA-2022:2139 is a vulnerability in tlog, published on 10 May 2022. 

### Official description

Tlog is a terminal I/O recording program similar to "script", but used in place of a user's shell, starting the recording and executing the real user's
shell afterwards. The recorded I/O can then be forwarded to a logging server
in JSON format.

Bug Fix(es) and Enhancement(s):

* tlog causing SSH to not reliably run commands (BZ#2077473)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tlog` | AlmaLinux:8 | All versions | 12.1-1.el8_6 |

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

Apply the vendor's patch.

## Is ALBA-2022:2139 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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