Bug 1163584 – CVE-2014-8710 wireshark: SigComp dissector crash (wnpa-sec-2014-20)

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1163584 - (CVE-2014-8710) CVE-2014-8710 wireshark: SigComp dissector crash (wnpa-sec-2014-20)

Summary:	CVE-2014-8710 wireshark: SigComp dissector crash (wnpa-sec-2014-20)

Status:	CLOSED ERRATA

Aliases:	CVE-2014-8710

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=moderate,public=20141104,repor...
Keywords:	Security

Depends On:	1163585 1208005 1245763
Blocks:	1163586 1210268
	Show dependency tree / graph

Reported:	2014-11-12 23:29 EST by Murray McAllister
Modified:	2015-11-24 07:21 EST (History)
CC List:	6 users (show)

See Also:
Fixed In Version:	wireshark 1.12.2, wireshark 1.10.11
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-11-19 23:47:57 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2015:1460	normal	SHIPPED_LIVE	Moderate: wireshark security, bug fix, and enhancement update	2015-07-21 10:14:59 EDT
Red Hat Product Errata	RHSA-2015:2393	normal	SHIPPED_LIVE	Moderate: wireshark security, bug fix, and enhancement update	2015-11-19 06:03:11 EST

Groups: None (edit)

Description Murray McAllister 2014-11-12 23:29:51 EST

It was reported that Wireshark's SigComp dissector could crash. It may be possible to make Wireshark crash by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file.

This is reported to affect Wireshark versions 1.10.0 to 1.10.10. It is fixed in versions 1.12.2 and 1.10.11.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10662

The version of Wireshark in Red Hat Enterprise Linux 5 and 6 is older than 1.10.x, and may not be affected. The version of Wireshark in Red Hat Enterprise Linux 7 is affected.

External References:

https://www.wireshark.org/security/wnpa-sec-2014-20.html

Comment 1 Murray McAllister 2014-11-12 23:33:18 EST

Created wireshark tracking bugs for this issue:

Affects: fedora-all [bug 1163585]

Comment 2 Siddharth Sharma 2014-11-14 07:38:46 EST

upstream fix
------------

Patch1:  https://code.wireshark.org/review/gitweb?p=wireshark.git;a=patch;h=9a2e8ead5c93e5af78881fb1c0e1ac4d648e2d58

Comment 3 Fedora Update System 2014-12-04 01:22:13 EST

wireshark-1.10.11-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 6 Siddharth Sharma 2015-01-14 14:16:39 EST

Analysis
========

In the code of Wireshark's SigComp dissector, calling of following function could lead to crash by largely increasing the value of 'n'  
...
proto_tree_add_string(udvm_tree,hf_id, bytecode_tvb, 0, 0, bytes_to_str(sha1_digest_buf, state_minimum_access_length_buff[n]));
...

Comment 9 errata-xmlrpc 2015-07-22 03:24:04 EDT

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 6

Via RHSA-2015:1460 https://rhn.redhat.com/errata/RHSA-2015-1460.html

Comment 16 errata-xmlrpc 2015-11-19 07:36:52 EST

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2015:2393 https://rhn.redhat.com/errata/RHSA-2015-2393.html

Comment 17 Huzaifa S. Sidhpurwala 2015-11-19 23:47:57 EST

Statement:

This issue affects the verison of wireshark as shipped with Red Hat Enterprsie Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates.

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