# ALBA-2022:4744: sos bug fix and enhancement update

> The sos utility update fixes a bug causing excessive memory usage and potential out-of-memory conditions during report generation.

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

## What is ALBA-2022:4744?

ALBA-2022:4744 is a vulnerability in sos, published on 25 May 2022. 

### Official description

The sos package contains a set of utilities that gather information from
system hardware, logs, and configuration files. The information can then be
used for diagnostic purposes and debugging.

Bug Fix(es) and Enhancement(s):

* sos collect fails to get node list from a pacemaker cluster (BZ#2071695)
* Tracker for 8.6 sos OCP focused async release (BZ#2071824)
* sosreport causes out-of-memory with excessive memory usage (BZ#2071825)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sos` | AlmaLinux:8 | All versions | 4.2-19.el8_6.alma |
| `sos-audit` | AlmaLinux:8 | All versions | 4.2-19.el8_6.alma |

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

Apply the vendor's patch.

## Is ALBA-2022:4744 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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