Skip to content
Fencer Intel
medium 5.0

CVE-2013-3555 json

epan/dissectors/packet-gtpv2.c in the GTPv2 dissector in Wireshark 1.8.x before 1.8.7 calls incorrect functions in certain contexts related…

published 13y ago modified 4mo ago also EUVD-2013-3490

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

Summary

epan/dissectors/packet-gtpv2.c in the GTPv2 dissector in Wireshark 1.8.x before 1.8.7 calls incorrect functions in certain contexts related to ciphers, which allows remote attackers to cause a denial of service (application crash) via a malformed packet.

Patch / fix

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

debian advisories DEBIAN-CVE-2013-3555

  • wireshark openSUSE Tumbleweed 2.2.2-1.1

opensuse advisories openSUSE-SU-2024:10199-1

Is CVE-2013-3555 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-2013-3555 updated cvss 4.3

wireshark: DoS (crash) in the GTPv2 dissector (wnpa-sec-2013-24, upstream #8493)

  • Red Hat Enterprise Linux 5 wireshark Red Hat Enterprise Linux 6 wireshark, wireshark-gnome
    not affected: vulnerable code not present

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.41% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • bugs.wireshark.org https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8493 referenced PoC, tagged "exploit" by a source, unverified

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-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.