Skip to content
Fencer Intel
medium 4.3

CVE-2015-7830 json

The pcapng_read_if_descr_block function in wiretap/pcapng.c in the pcapng parser in Wireshark 1.12.x before 1.12.8 uses too many levels of…

published 2015-11-15 10 y ago modified 2026-06-17 4 mo ago also EUVD-2015-7728

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.5%
EPSS 3.5% chance of exploitation in 30 days, percentile 89%
public exploits
0
none known

Summary

The pcapng_read_if_descr_block function in wiretap/pcapng.c in the pcapng parser in Wireshark 1.12.x before 1.12.8 uses too many levels of pointer indirection, which allows remote attackers to cause a denial of service (incorrect free and application crash) via a crafted packet that triggers interface-filter copying.

Patch / fix

  • wireshark Debian 14, Debian 13, Debian 12 1.12.8+g5b6e543-1

debian advisories DEBIAN-CVE-2015-7830

  • wireshark SLES for SAP 11 SP4, SLES for SAP 11 SP3, SLES 11 SP4 +6 more 1.12.9-0.12.1
  • wireshark SLES for SAP 12 SP1, SLES for SAP 12, SLES 12 SP1 +5 more 1.12.9-22.1

suse advisories SUSE-SU-2016:0110-1SUSE-SU-2016:0109-1

  • wireshark openSUSE Tumbleweed 2.2.2-1.1

opensuse advisories openSUSE-SU-2024:10199-1

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-2015-7830 updated cvss 4.4

wireshark: Pcapng file parser crash

  • 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

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

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-20 Improper Input Validation

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.