Skip to content
Fencer Intel
medium 4.3

CVE-2011-3483 json

Wireshark 1.6.x before 1.6.2 allows remote attackers to cause a denial of service (application crash) via a malformed capture file that lea…

published 2011-09-20 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-3446

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

Summary

Wireshark 1.6.x before 1.6.2 allows remote attackers to cause a denial of service (application crash) via a malformed capture file that leads to an invalid root tvbuff, related to a "buffer exception handling vulnerability."

Patch / fix

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

debian advisories DEBIAN-CVE-2011-3483

  • 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-2011-3483 updated cvss 4.3

Wireshark: buffer exception handling vulnerability

  • Red Hat All currently supported Red Hat products
    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-36128)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-36128 Wireshark 1.6.1 - Malformed Packet Trace File Remote Denial of Service dos, 2011-09-08

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