CVE-2012-1596: Medium severity Wireshark Wireshark vulnerability

Published Apr 11, 2012

Updated

The mp2tprocessfragmentedpayload function in epan/dissectors/packet-mp2t.c in the MP2T dissector in Wireshark 1.4.x before 1.4.12 and 1.6.x before 1.6.6 allows remote attackers to cause a denial of service (application crash) via a packet containing an invalid pointer value that triggers an incorrect memory-allocation attempt.

Affected Software

18 affected components

Wireshark Wireshark=1.4.0

Wireshark Wireshark=1.4.1

Wireshark Wireshark=1.4.2

Wireshark Wireshark=1.4.3

Wireshark Wireshark=1.4.4

Wireshark Wireshark=1.4.5

Wireshark Wireshark=1.4.6

Wireshark Wireshark=1.4.7

Wireshark Wireshark=1.4.8

Wireshark Wireshark=1.4.9

Wireshark Wireshark=1.4.10

Wireshark Wireshark=1.4.11

Wireshark Wireshark=1.6.0

Wireshark Wireshark=1.6.1

Wireshark Wireshark=1.6.2

Wireshark Wireshark=1.6.3

Wireshark Wireshark=1.6.4

Wireshark Wireshark=1.6.5

Event History

Apr 11, 2012

CVE Published

via MITRE·10:00 AM

Data Sourced

via MITRE·10:00 AM

Description

Frequently Asked Questions

What is the severity of CVE-2012-1596?

CVE-2012-1596 has been classified as a denial of service vulnerability that can lead to application crashes.

How do I fix CVE-2012-1596?

To fix CVE-2012-1596, you should update Wireshark to version 1.4.12 or later, or 1.6.6 or later.

Which versions of Wireshark are affected by CVE-2012-1596?

Wireshark versions 1.4.0 through 1.4.11 and 1.6.0 through 1.6.5 are affected by CVE-2012-1596.

Is CVE-2012-1596 exploitable remotely?

Yes, CVE-2012-1596 can be exploited by remote attackers through specially crafted packets.

What impact does CVE-2012-1596 have on Wireshark users?

Users of affected Wireshark versions may experienced crashes when processing malformed MP2T packets due to CVE-2012-1596.