# CVE-2015-8012: Denial of service in n/a

> Remote attackers can crash the LLDP daemon via malformed packets, causing a denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 28 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-8012, GHSA-26h8-43q7-4r2w

## What is CVE-2015-8012?

CVE-2015-8012 is a high-severity denial of service vulnerability in n/a, published on 28 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

lldpd before 0.8.0 allows remote attackers to cause a denial of service (assertion failure and daemon crash) via a malformed packet.

Weakness: CWE-617 (Reachable Assertion)

## Which versions are affected by CVE-2015-8012?

It affects 1 product.


Products: Lldpd Project Lldpd.

## How do I fix CVE-2015-8012?

Upgrade to a fixed version.

## Is CVE-2015-8012 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-41910](https://insights.sbomify.com/CVE-2023-41910/): Memory corruption in n/a (critical 9.8)
- [CVE-2026-46433](https://insights.sbomify.com/CVE-2026-46433/): lldpd: Heap OOB Read in VLAN Decapsulation memmove (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-8012 and fix it if it is affected.

What it is: CVE-2015-8012 is a high-severity denial of service vulnerability in n/a, published on 28 Jan 2020. 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-2015-8012 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-2015-8012/ (Markdown: https://insights.sbomify.com/CVE-2015-8012/index.md)
```

## Sources

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

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