# ALBA-2022:0355: frr bug fix update

> An attacker can cause a denial of service by triggering crashes in the FRRouting daemon through invalid BFD configurations or specific network conditions.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Feb 2022

## What is ALBA-2022:0355?

ALBA-2022:0355 is a denial of service vulnerability in frr, published on 1 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FRRouting is free software that manages TCP/IP based routing protocols. It takes a multi-server and multi-threaded approach to resolve the current complexity of the Internet. FRRouting supports BGP4, OSPFv2, OSPFv3, ISIS, RIP, RIPng, PIM, NHRP, PBR, EIGRP, and BFD.

Bug Fix(es):

* FRR reloader generating invalid BFD configurations, exits with error
(BZ#2031077)

* Bfdd crash in metallb CI (BZ#2037200)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `frr` | AlmaLinux:8 | All versions | 7.5-4.el8_5.2 |

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

Apply the vendor's patch.

## Is ALBA-2022:0355 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: ALBA-2022:0355 is a denial of service vulnerability in frr, published on 1 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of ALBA-2022:0355 in the wild and no public exploit code.

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

## Sources

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

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