# ALBA-2022:0901: firewalld bug fix and enhancement update

> Adding large numbers of ipsets causes significant delays in firewalld, potentially leading to service unavailability or degraded performance.

- **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:** 15 Mar 2022

## What is ALBA-2022:0901?

ALBA-2022:0901 is a denial of service vulnerability in firewall-applet, published on 15 Mar 2022. 

### Official description

firewalld is a firewall service daemon that provides a dynamic customizable
firewall with a D-Bus interface.

Bug Fix(es) and Enhancement(s):

* firewall-cmd takes hours when adding 55K ipsets (BZ#2046343)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `firewall-applet` | AlmaLinux:8 | All versions | 0.9.3-7.el8_5.1 |
| `firewall-config` | AlmaLinux:8 | All versions | 0.9.3-7.el8_5.1 |

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

Apply the vendor's patch.

## Is ALBA-2022:0901 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2022:0901 is a denial of service vulnerability in firewall-applet, published on 15 Mar 2022. 
Exploitation: There is no known exploitation of ALBA-2022:0901 in the wild and no public exploit code.

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

## Sources

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

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