# ALBA-2021:3594: libdb bug fix and enhancement update

> A bug in the Berkeley DB library causes the rpm command to hang and consume 100% CPU, leading to a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Sep 2021

## What is ALBA-2021:3594?

ALBA-2021:3594 is a denial of service vulnerability in libdb, published on 21 Sep 2021. 

### Official description

The libdb packages provide the Berkeley Database, an embedded database
supporting both traditional and client/server applications.

Bug Fix(es) and Enhancement(s):

* [FJ8.4 Bug]: [REG]The rpm command hangs and the CPU usage reaches 100%
(BZ#2001972)

## Which versions are affected by ALBA-2021:3594?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libdb` | AlmaLinux:8 | All versions | 5.3.28-42.el8_4 |
| `libdb-cxx` | AlmaLinux:8 | All versions | 5.3.28-42.el8_4 |
| `libdb-cxx-devel` | AlmaLinux:8 | All versions | 5.3.28-42.el8_4 |
| `libdb-devel` | AlmaLinux:8 | All versions | 5.3.28-42.el8_4 |
| `libdb-devel-doc` | AlmaLinux:8 | All versions | 5.3.28-42.el8_4 |
| `libdb-sql` | AlmaLinux:8 | All versions | 5.3.28-42.el8_4 |
| `libdb-sql-devel` | AlmaLinux:8 | All versions | 5.3.28-42.el8_4 |
| `libdb-utils` | AlmaLinux:8 | All versions | 5.3.28-42.el8_4 |

## How do I fix ALBA-2021:3594?

Apply the vendor's patch.

## Is ALBA-2021:3594 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2021:3594 is a denial of service vulnerability in libdb, published on 21 Sep 2021. 
Exploitation: There is no known exploitation of ALBA-2021:3594 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2021:3594

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