# CVE-2024-44070: Denial of service in n/a

> Attackers can cause a denial of service in FRRouting by sending malformed BGP attributes that bypass length checks.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Aug 2024
- **Updated:** 4 Nov 2025
- **Also known as:** AZL-47862, AZL-47868, CLSA-2025-1738265190, DEBIAN-CVE-2024-44070, GHSA-88xw-q94w-q9mr, SUSE-SU-2024:3090-1, SUSE-SU-2024:3108-1, UBUNTU-CVE-2024-44070, USN-7016-1, USN-7017-1, USN-7230-1, openSUSE-SU-2024:14286-1

## What is CVE-2024-44070?

CVE-2024-44070 is a critical denial of service vulnerability in Redhat Enterprise Linux, published on 19 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in FRRouting (FRR) through 10.1. bgp_attr_encap in bgpd/bgp_attr.c does not check the actual remaining stream length before taking the TLV value.

## Which versions are affected by CVE-2024-44070?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `frr` | SUSE:Enterprise Storage 7.1 | All versions | 7.4-150300.4.29.1 |
| `frr` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 7.4-150300.4.29.1 |
| `frr` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 7.4-150300.4.29.1 |
| `frr` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 7.4-150300.4.29.1 |
| `frr` | SUSE:Linux Enterprise Module for Server Applications 15 SP5 | All versions | 8.4-150500.4.26.1 |
| `frr` | SUSE:Linux Enterprise Module for Server Applications 15 SP6 | All versions | 8.4-150500.4.26.1 |
| `frr` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 7.4-150300.4.29.1 |
| `frr` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 7.4-150300.4.29.1 |
| `frr` | SUSE:Linux Enterprise Server for SAP Applications 15 SP3 | All versions | 7.4-150300.4.29.1 |
| `frr` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 7.4-150300.4.29.1 |
| `frr` | SUSE:Manager Proxy 4.3 | All versions | 7.4-150300.4.29.1 |
| `frr` | SUSE:Manager Server 4.3 | All versions | 7.4-150300.4.29.1 |
| `frr` | openSUSE:Leap 15.5 | All versions | 8.4-150500.4.26.1 |
| `frr` | openSUSE:Leap 15.6 | All versions | 8.4-150500.4.26.1 |
| `frr` | openSUSE:Tumbleweed | All versions | 10.0.1-2.1 |

Products: Frrouting Frrouting, Redhat Enterprise Linux.

## How do I fix CVE-2024-44070?

Apply the vendor's patch.

## Is CVE-2024-44070 being exploited?

There is no known exploitation of CVE-2024-44070 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Enterprise Linux

- [CVE-2023-38406](https://insights.sbomify.com/CVE-2023-38406/): bgpd/bgp_flowspec.c in FRRouting (FRR) before 8.4.3 mishandles an nlri length of zero, aka a "flowspec overflow." (critical 9.8)
- [CVE-2022-37035](https://insights.sbomify.com/CVE-2022-37035/): Use after free in n/a (high 8.1)
- [CVE-2022-26127](https://insights.sbomify.com/CVE-2022-26127/): Memory corruption in FRRouting (high 7.8)
- [CVE-2022-26128](https://insights.sbomify.com/CVE-2022-26128/): Memory corruption in FRRouting (high 7.8)
- [CVE-2022-26129](https://insights.sbomify.com/CVE-2022-26129/): Memory corruption in FRRouting (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-44070 and fix it if it is affected.

What it is: CVE-2024-44070 is a critical denial of service vulnerability in Redhat Enterprise Linux, published on 19 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-44070 in the wild and no public exploit code.

Affected product: Redhat Enterprise Linux. 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/CVE-2024-44070/ (Markdown: https://insights.sbomify.com/CVE-2024-44070/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-44070
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-44070
- OSV: https://osv.dev/vulnerability/CVE-2024-44070

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