# CVE-2016-4049: Denial of service in n/a

> Remote attackers can crash the Quagga BGP daemon by sending large packets, causing a denial of service.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 May 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5crg-85w6-wxj6, MGASA-2016-0165, SUSE-SU-2016:1482-1, SUSE-SU-2016:1483-1, UBUNTU-CVE-2016-4049

## What is CVE-2016-4049?

CVE-2016-4049 is a high-severity denial of service vulnerability in Opensuse Leap, published on 23 May 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The bgp_dump_routes_func function in bgpd/bgp_dump.c in Quagga does not perform size checks when dumping data, which might allow remote attackers to cause a denial of service (assertion failure and daemon crash) via a large BGP packet.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2016-4049?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `quagga` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 0.99.15-0.24.2 |
| `quagga` | SUSE:Linux Enterprise Server 12 | All versions | 0.99.22.1-12.1 |
| `quagga` | SUSE:Linux Enterprise Server 12 SP1 | All versions | 0.99.22.1-12.1 |
| `quagga` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 0.99.15-0.24.2 |
| `quagga` | SUSE:Linux Enterprise Server for SAP Applications 12 | All versions | 0.99.22.1-12.1 |
| `quagga` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 0.99.22.1-12.1 |
| `quagga` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 0.99.15-0.24.2 |
| `quagga` | SUSE:Linux Enterprise Software Development Kit 12 | All versions | 0.99.22.1-12.1 |
| `quagga` | SUSE:Linux Enterprise Software Development Kit 12 SP1 | All versions | 0.99.22.1-12.1 |

Products: Opensuse Leap, Opensuse Opensuse, Quagga Quagga.

## How do I fix CVE-2016-4049?

Apply the vendor's patch.

## Is CVE-2016-4049 being exploited?

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

## Other vulnerabilities in Opensuse Leap

- [CVE-2015-4902](https://insights.sbomify.com/CVE-2015-4902/): Oracle Java SE Integrity Check (medium 5.3, exploited in the wild)
- [CVE-2017-14804](https://insights.sbomify.com/CVE-2017-14804/): package builds could use directory traversal to write outside of target area (critical 9.9)
- [CVE-2019-20787](https://insights.sbomify.com/CVE-2019-20787/): Teeworlds before 0.7.4 has an integer overflow when computing a tilemap size. (critical 9.8)
- [CVE-2019-8341](https://insights.sbomify.com/CVE-2019-8341/): Code injection in n/a (critical 9.8)
- [CVE-2019-6438](https://insights.sbomify.com/CVE-2019-6438/): Other in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-4049 and fix it if it is affected.

What it is: CVE-2016-4049 is a high-severity denial of service vulnerability in Opensuse Leap, published on 23 May 2016. 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-2016-4049 in the wild and no public exploit code.

Affected product: Opensuse Leap. 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-2016-4049/ (Markdown: https://insights.sbomify.com/CVE-2016-4049/index.md)
```

## Sources

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

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