# CVE-2019-5608: Memory corruption in FreeBSD

> A remote attacker can cause a kernel panic via crafted ICMPv6 packets, leading to denial of service on FreeBSD systems.

- **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:** No
- **Published:** 29 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m5pq-g347-cqr6

## What is CVE-2019-5608?

CVE-2019-5608 is a critical memory corruption vulnerability in Freebsd Freebsd, published on 29 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In FreeBSD 12.0-STABLE before r350648, 12.0-RELEASE before 12.0-RELEASE-p9, 11.3-STABLE before r350650, 11.3-RELEASE before 11.3-RELEASE-p2, and 11.2-RELEASE before 11.2-RELEASE-p13, the ICMPv6 input path incorrectly handles cases where an MLDv2 listener query packet is internally fragmented across multiple mbufs. A remote attacker may be able to cause an out-of-bounds read or write that may cause the kernel to attempt to access an unmapped page and subsequently panic.

Weakness: CWE-787 (Out-of-bounds Write), CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2019-5608?

It affects 2 products.


Products: Freebsd Freebsd, Netapp Clustered Data Ontap.

## How do I fix CVE-2019-5608?

No fix has been published for CVE-2019-5608 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-5608 being exploited?

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

## Other vulnerabilities in Freebsd Freebsd

- [CVE-2018-17160](https://insights.sbomify.com/CVE-2018-17160/): Memory corruption in FreeBSD (critical 10.0)
- [CVE-2014-3954](https://insights.sbomify.com/CVE-2014-3954/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-4304](https://insights.sbomify.com/CVE-2006-4304/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-0226](https://insights.sbomify.com/CVE-2006-0226/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0002](https://insights.sbomify.com/CVE-2004-0002/): Denial of service in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-5608 and fix it if it is affected.

What it is: CVE-2019-5608 is a critical memory corruption vulnerability in Freebsd Freebsd, published on 29 Aug 2019. 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-2019-5608 in the wild and no public exploit code.

Affected product: Freebsd Freebsd. 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-2019-5608/ (Markdown: https://insights.sbomify.com/CVE-2019-5608/index.md)
```

## Sources

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

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