Skip to content
Fencer Intel
medium 5.0

CVE-2015-3813 json

The fragment_add_work function in epan/reassemble.c in the packet-reassembly feature in Wireshark 1.12.x before 1.12.5 does not properly de…

published 11y ago modified 4mo ago also EUVD-2015-3849

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

Summary

The fragment_add_work function in epan/reassemble.c in the packet-reassembly feature in Wireshark 1.12.x before 1.12.5 does not properly determine the defragmentation state in a case of an insufficient snapshot length, which allows remote attackers to cause a denial of service (memory consumption) via a crafted packet.

Patch / fix

  • wireshark Debian 14, Debian 13, Debian 12 1.12.5+g5819e5b-1

debian advisories DEBIAN-CVE-2015-3813

  • wireshark RHEL 6 1.8.10-25.el6
  • wireshark-gnome RHEL 6 1.8.10-25.el6
  • wireshark RHEL 7 1.10.14-7.el7
  • wireshark-gnome RHEL 7 1.10.14-7.el7

red hat advisories RHSA-2017:0631RHSA-2015:2393

  • wireshark SLES 11 SP4, SLES 11 SP3-TERADATA, SLES 11 SP3 +6 more 1.12.7-0.5.3
  • wireshark SLES for SAP 12, SLES 12, SLED 12 +1 more 1.12.7-15.1
  • wireshark SLES for SAP 12, SLES 12, SLED 12 +1 more 1.10.14-12.1

suse advisories SUSE-SU-2015:1676-2SUSE-SU-2015:1676-1SUSE-SU-2015:1713-1SUSE-SU-2015:1046-1

  • wireshark openSUSE Tumbleweed 2.2.2-1.1

opensuse advisories openSUSE-SU-2024:10199-1

Is CVE-2015-3813 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-3813 updated cvss 4.3

wireshark: Reassembly memory leak (wnpa-sec-2015-16)

  • Red Hat Enterprise Linux 5 wireshark
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux Client (v. 7) wireshark 1.10.14-7.el7, wireshark-gnome 1.10.14-7.el7 Red Hat Enterprise Linux Client Optional (v. 7) wireshark-devel 1.10.14-7.el7, wireshark-debuginfo 1.10.14-7.el7
    fixed: vendor fix RHSA-2015:2393
  • Red Hat Enterprise Linux Desktop (v. 6) wireshark 1.8.10-25.el6, wireshark-gnome 1.8.10-25.el6 Red Hat Enterprise Linux Desktop Optional (v. 6) wireshark-devel 1.8.10-25.el6, wireshark-debuginfo 1.8.10-25.el6 Red Hat Enterprise Linux Server (v. 6) wireshark 1.8.10-25.el6, wireshark-gnome 1.8.10-25.el6
    fixed: vendor fix RHSA-2017:0631
  • Red Hat Enterprise Linux Server (v. 7) wireshark 1.10.14-7.el7, wireshark-gnome 1.10.14-7.el7
    fixed: vendor fix RHSA-2015:2393
  • Red Hat Enterprise Linux Server Optional (v. 6) wireshark-devel 1.8.10-25.el6, wireshark-debuginfo 1.8.10-25.el6
    fixed: vendor fix RHSA-2017:0631
  • Red Hat Enterprise Linux Server Optional (v. 7) wireshark-devel 1.10.14-7.el7, wireshark-debuginfo 1.10.14-7.el7
    fixed: vendor fix RHSA-2015:2393
  • Red Hat Enterprise Linux Workstation (v. 6) wireshark 1.8.10-25.el6, wireshark-gnome 1.8.10-25.el6
    fixed: vendor fix RHSA-2017:0631
  • Red Hat Enterprise Linux Workstation (v. 7) wireshark 1.10.14-7.el7, wireshark-gnome 1.10.14-7.el7
    fixed: vendor fix RHSA-2015:2393
show 2 more
  • Red Hat Enterprise Linux Workstation Optional (v. 6) wireshark-devel 1.8.10-25.el6, wireshark-debuginfo 1.8.10-25.el6
    fixed: vendor fix RHSA-2017:0631
  • Red Hat Enterprise Linux Workstation Optional (v. 7) wireshark-devel 1.10.14-7.el7, wireshark-debuginfo 1.10.14-7.el7
    fixed: vendor fix RHSA-2015:2393

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

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

CVSS scores

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

Classification

Weakness
  • CWE-399 Resource Management Errors

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.