Skip to content
Fencer Intel
medium 5.5

CVE-2017-9616 json

In Wireshark 2.2.7, overly deep mp4 chunks may cause stack exhaustion (uncontrolled recursion) in the dissect_mp4_box function in epan/diss…

published 2017-06-14 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-18547

cvss
5.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 64%
public exploits
0
none known

Summary

In Wireshark 2.2.7, overly deep mp4 chunks may cause stack exhaustion (uncontrolled recursion) in the dissect_mp4_box function in epan/dissectors/file-mp4.c.

Patch / fix

  • wireshark Debian 14, Debian 13, Debian 12 2.4.0-1

debian advisories DEBIAN-CVE-2017-9616

  • wireshark Ubuntu 14.04 LTS 2.6.3-1~ubuntu14.04.1
  • wireshark Ubuntu 16.04 LTS 2.6.3-1~ubuntu16.04.1
  • wireshark Ubuntu 18.04 LTS 2.6.3-1~ubuntu18.04.1

ubuntu advisories UBUNTU-CVE-2017-9616

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-9616 updated cvss 3.3

wireshark: Overly deep mp4 chunks may cause stack exhaustion

  • Red Hat Enterprise Linux 5 wireshark Red Hat Enterprise Linux 6 wireshark, wireshark-gnome Red Hat Enterprise Linux 7 wireshark, wireshark-gnome
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.03% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 5.5 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.