Bug 512987 - (CVE-2009-2562) CVE-2009-2562 Wireshark: Integer overflow in the AFS dissector
CVE-2009-2562 Wireshark: Integer overflow in the AFS dissector
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
: Security
Depends On: 549581 549582 549583 549584 561099 833992
  Show dependency treegraph
Reported: 2009-07-21 11:01 EDT by Jan Lieskovsky
Modified: 2016-03-04 05:44 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-04-20 11:54:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jan Lieskovsky 2009-07-21 11:01:35 EDT
An integer overflow flaw, leading to heap-based buffer overflow was found
in the Wiresharks's AFS dissector. A remote attacker could provide
a specially-crafted AFS packet capture file, which once opened by an
unsuspecting user would lead to denial of service (Wireshark crash).



Upstream patch:
Comment 2 Jan Lieskovsky 2009-07-21 11:09:03 EDT
This issue affects the versions of the Wireshark package, as shipped
with Red Hat Enteprise Linux 3, 4, and 5.

This issue affects the versions of the Wireshark package, as shipped
with Fedora releases of 10, 11, and Rawhide.
Comment 3 Jan Lieskovsky 2009-07-21 15:49:50 EDT
MITRE's CVE-2009-2562 entry:

Unspecified vulnerability in the AFS dissector in Wireshark 0.9.2
through 1.2.0 allows remote attackers to cause a denial of service
(crash) via unknown vectors.

Comment 5 Jan Lieskovsky 2009-08-12 06:06:19 EDT
Official statement from Red Hat Security Response Team regarding this issue:

The Red Hat Security Response Team has rated this issue as having
low security impact, a future Wireshark package update may
address this flaw in Red Hat Enterprise Linux 3, 4, and 5. More
information regarding issue severity can be found here:
Comment 8 Tomas Hoger 2009-09-30 09:28:39 EDT
This really is caused by an integer overflow as indicated in comment #0.  i_orxs value is read from the dump.  It's later passed to tvb_get_ptr() for sanity-checking, however, that does not report a problem when i_orxs is 0xFFFFFFFF.  The reason is that this value is casted from unsigned to signed integer type in compute_offset_length(), i.e. it becomes -1 and that is a special value in compute_offset_length() - which means "to the end of the data".

Later, ep_alloc() is called as ep_alloc(i_orxs+1), hence with size equal to 0, allocating buffer of insufficient size.  That buffer is later filled with memcpy as memcpy(tmp_orxs, p_orxs, i_orxs).  This attempts to copy ~4 gig of data and is likely to trigger SEGV when trying to read or write from an unmapped memory.
Comment 10 Fedora Update System 2009-11-04 07:02:25 EST
wireshark-1.2.2-1.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 11 Fedora Update System 2009-12-04 18:38:56 EST
wireshark-1.2.1-1.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 14 errata-xmlrpc 2010-04-20 11:31:19 EDT
This issue has been addressed in following products:

  Red Hat Enterprise Linux 4
  Red Hat Enterprise Linux 5
  Red Hat Enterprise Linux 3

Via RHSA-2010:0360 https://rhn.redhat.com/errata/RHSA-2010-0360.html

Note You need to log in before you can comment on or make changes to this bug.