# CVE-2018-5379: Use after free in bgpd

> A double-free vulnerability in the Quagga BGP daemon allows remote attackers to cause a denial of service or execute arbitrary code via crafted UPDATE messages.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Feb 2018
- **Updated:** 17 Sep 2024
- **Also known as:** CVE-2018-1000063, GHSA-5prq-47x2-38gv, RHSA-2018:0377, UBUNTU-CVE-2018-5379

## What is CVE-2018-5379?

CVE-2018-5379 is a high-severity use after free vulnerability in Canonical Ubuntu Linux, published on 19 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Quagga BGP daemon (bgpd) prior to version 1.2.3 can double-free memory when processing certain forms of UPDATE message, containing cluster-list and/or unknown attributes. A successful attack could cause a denial of service or potentially allow an attacker to execute arbitrary code.

Weakness: CWE-415 (Double Free)

## Which versions are affected by CVE-2018-5379?

It affects 9 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `quagga` | Red Hat:enterprise_linux:7::server | All versions | 0:0.99.22.4-5.el7_4 |
| `quagga-contrib` | Red Hat:enterprise_linux:7::server | All versions | 0:0.99.22.4-5.el7_4 |
| `quagga-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:0.99.22.4-5.el7_4 |
| `quagga-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:0.99.22.4-5.el7_4 |
| `quagga` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.99.22.4-5.el7_4 |
| `quagga-contrib` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.99.22.4-5.el7_4 |
| `quagga-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.99.22.4-5.el7_4 |
| `quagga-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.99.22.4-5.el7_4 |

Products: Canonical Ubuntu Linux, Debian Debian Linux, Quagga Quagga, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Eus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Workstation, Siemens Ruggedcom Rox Ii Firmware.

## How do I fix CVE-2018-5379?

Upgrade to a fixed version.

## Is CVE-2018-5379 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-5379 and fix it if it is affected.

What it is: CVE-2018-5379 is a high-severity use after free vulnerability in Canonical Ubuntu Linux, published on 19 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-5379 in the wild and no public exploit code.

Affected product: Canonical Ubuntu 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-2018-5379/ (Markdown: https://insights.sbomify.com/CVE-2018-5379/index.md)
```

## Sources

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

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