Skip to content
Fencer Intel
low 3.3

CVE-2012-2393 json

epan/dissectors/packet-diameter.c in the DIAMETER dissector in Wireshark 1.4.x before 1.4.13 and 1.6.x before 1.6.8 does not properly const…

published 2012-06-30 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-2381

cvss
3.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.7%
EPSS 3.7% chance of exploitation in 30 days, percentile 89%
public exploits
1
Exploit-DB

Summary

epan/dissectors/packet-diameter.c in the DIAMETER dissector in Wireshark 1.4.x before 1.4.13 and 1.6.x before 1.6.8 does not properly construct certain array data structures, which allows remote attackers to cause a denial of service (application crash) via a crafted packet that triggers incorrect memory allocation.

Patch / fix

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

debian advisories DEBIAN-CVE-2012-2393

  • 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-2012-2393 updated cvss 4.3

wireshark: Memory allocation flaw in the DIAMETER dissector (wnpa-sec-2012-09)

  • 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

Timeline

  1. First public exploit (EDB-18918)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-18918 Wireshark - DIAMETER Dissector Denial of Service dos, 2012-05-24

CVSS scores

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

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

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.