Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2015-8736

wireshark: MP2T file parser crash (wnpa-sec-2015-54)

Overview

Published
4 Jan 2016
Modified
6 May 2026
Medium CVE
0 Registry packages
4 OS packages
4 Linux distributions
Yes Fix available

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.

Source: OX vulnerability database

Severity

5.5 · MEDIUM

CVSS 3.0 base score, scored by NVD.

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Weakness: CWE-20

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 8 fixes

debian 4 releases · 1 package

fixed 4
wireshark
debian fixes for CVE-2015-8736
ReleasePackageFixed in
11 wireshark 2.0.1+g59ea380-1
12 wireshark 2.0.1+g59ea380-1
13 wireshark 2.0.1+g59ea380-1
14 wireshark 2.0.1+g59ea380-1

echo 1 release · 1 package

fixed 1
wireshark
echo fixes for CVE-2015-8736
ReleasePackageFixed in
wireshark 2.0.1+g59ea380-1

openSUSE 1 release · 1 package

fixed 1
wireshark
openSUSE fixes for CVE-2015-8736
ReleasePackageFixed inAdvisory
Tumbleweed wireshark +3 2.2.2-1.1 openSUSE-SU-2024:10199-1

ubuntu 2 releases · 1 package

fixed 2
wireshark
ubuntu fixes for CVE-2015-8736
ReleasePackageFixed in
18.04 wireshark 2.6.3-1~ubuntu18.04.1
18.04-ESM wireshark 2.6.3-1~ubuntu18.04.1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.