# CVE-2024-27913: Null dereference in n/a

> Remote attackers can crash the FRRouting OSPF daemon by sending malformed OSPF LSA packets, causing a denial of service.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Feb 2024
- **Updated:** 26 Mar 2025
- **Also known as:** AZL-35450, DEBIAN-CVE-2024-27913, GHSA-46v4-9j9w-fv79, UBUNTU-CVE-2024-27913, USN-6679-1, openSUSE-SU-2024:13911-1

## What is CVE-2024-27913?

CVE-2024-27913 is a medium-severity vulnerability in n/a, published on 28 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ospf_te_parse_te in ospfd/ospf_te.c in FRRouting (FRR) through 9.1 allows remote attackers to cause a denial of service (ospfd daemon crash) via a malformed OSPF LSA packet, because of an attempted access to a missing attribute field.

Weakness: CWE-909 (Missing Initialization of Resource)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `frr` | openSUSE:Tumbleweed | All versions | 8.4-11.1 |

Products: Frrouting Frrouting.

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

Apply the vendor's patch.

## Is CVE-2024-27913 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-44070](https://insights.sbomify.com/CVE-2024-44070/): Denial of service in n/a (critical 9.8)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-27913 is a medium-severity vulnerability in n/a, published on 28 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-27913 in the wild and no public exploit code.

Affected product: n/a. 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-27913/ (Markdown: https://insights.sbomify.com/CVE-2024-27913/index.md)
```

## Sources

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

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