Bug 1272016 (CVE-2015-7830) - CVE-2015-7830 wireshark: Pcapng file parser crash
Summary: CVE-2015-7830 wireshark: Pcapng file parser crash
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2015-7830
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1272020
Blocks: 1272019
TreeView+ depends on / blocked
 
Reported: 2015-10-15 09:45 UTC by Adam Mariš
Modified: 2021-02-17 04:50 UTC (History)
6 users (show)

Fixed In Version: wireshark 1.12.8
Clone Of:
Environment:
Last Closed: 2015-10-26 16:46:38 UTC
Embargoed:


Attachments (Terms of Use)

Description Adam Mariš 2015-10-15 09:45:18 UTC
A vulnerability was found in wireshark causing the pcapng parser to crash while copying an interface filter. Attacker could crash wireshark by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file.

Upstream patch:

https://bugs.wireshark.org/bugzilla/attachment.cgi?id=13807&action=diff

External reference:

https://www.wireshark.org/security/wnpa-sec-2015-30.html

Comment 1 Adam Mariš 2015-10-15 09:51:11 UTC
Created wireshark tracking bugs for this issue:

Affects: fedora-all [bug 1272020]

Comment 2 Stefan Cornelius 2015-10-26 16:04:02 UTC
So, the root cause is using the address of an pointer instead of the pointer itself. This can lead to a stack-based memory corruption because the memcpy() copies into the stack space, where the pointer is located. Stack corruptions are problematic, since it may be possible to overwrite a return address or something similar. Since it doesn't overwrite the pointer directly but with an offset of 38h, it may be possible to align the stack in a way that would allow to overwrite something without disrupting, for example, stack canaries. The length of the memcpy() is controllable, too ... so bottom line, I wouldn't rule out code execution.

Comment 4 Kurt Seifried 2015-11-02 19:53:51 UTC
Statement:

This issue affects the versions of wireshark as shipped with Red Hat Enterprise Linux 5, 6 and 7. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.


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