# CVE-2015-8736: Memory corruption in n/a

> Remote attackers can cause a denial of service via a stack-based buffer overflow in Wireshark's MP2T parser using a crafted file.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Jan 2016
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-8736, GHSA-f7mh-8r75-ggrf, UBUNTU-CVE-2015-8736

## What is CVE-2015-8736?

CVE-2015-8736 is a medium-severity memory corruption vulnerability in Wireshark Wireshark, published on 4 Jan 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The mp2t_find_next_pcr function in wiretap/mp2t.c in the MP2T file parser in Wireshark 2.0.x before 2.0.1 does not reserve memory for a trailer, which allows remote attackers to cause a denial of service (stack-based buffer overflow and application crash) via a crafted file.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Wireshark Wireshark.

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

Upgrade to a fixed version.

## Is CVE-2015-8736 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-8736 exists.

Public exploit code:

- Wireshark - file_read 'wtap_read_bytes_or_eof/mp2t_find_next_pcr' Stack Buffer Overflow (exploitdb)

## Other vulnerabilities in Wireshark Wireshark

- [CVE-2011-0444](https://insights.sbomify.com/CVE-2011-0444/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-2994](https://insights.sbomify.com/CVE-2010-2994/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-2995](https://insights.sbomify.com/CVE-2010-2995/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-1266](https://insights.sbomify.com/CVE-2009-1266/): Other in n/a (critical 10.0)
- [CVE-2009-1210](https://insights.sbomify.com/CVE-2009-1210/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-8736 is a medium-severity memory corruption vulnerability in Wireshark Wireshark, published on 4 Jan 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-8736 exists.

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

## Sources

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

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