Bug 1684115 (CVE-2019-9214)

Summary:	CVE-2019-9214 wireshark: null-deference read in RPCAP dissector
Product:	[Other] Security Response	Reporter:	Dhananjay Arunesh <darunesh>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	denis, huzaifas, lemenkov, mruprich, msehnout, phatina, rvokal, sergey.avseyev
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	wireshark 2.6.7, wireshark 2.4.13	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-10 10:49:32 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1695977
Bug Blocks:	1684116

Description Dhananjay Arunesh 2019-02-28 13:20:28 UTC

In Wireshark 2.4.0 to 2.4.12 and 2.6.0 to 2.6.6, the RPCAP dissector could crash. This was addressed in epan/dissectors/packet-rpcap.c by avoiding an attempted dereference of a NULL conversation.

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

Upstream Patch:
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=c557bb0910be271e49563756411a690a1bc53ce5

Comment 1 Dhananjay Arunesh 2019-02-28 13:22:09 UTC

External References:

https://www.wireshark.org/security/wnpa-sec-2019-08.html

Comment 2 Stefan Cornelius 2019-03-11 15:15:12 UTC

Hrm. Seems like this was introduced via https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commitdiff;h=d58a3ffe4f69366f25fd192e41a89b4769c7d22c

That's a fairly recent commit and contradicts the versions upstream claims to be affected.

Comment 3 Michal Ruprich 2019-03-13 09:48:40 UTC

(In reply to Stefan Cornelius from comment #2)
> Hrm. Seems like this was introduced via
> https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commitdiff;
> h=d58a3ffe4f69366f25fd192e41a89b4769c7d22c
> 
> That's a fairly recent commit and contradicts the versions upstream claims
> to be affected.

Yes this seems to be the case.

Comment 4 Stefan Cornelius 2019-03-20 10:15:57 UTC

Statement:

This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 5, 6, and 7.

Comment 5 Pedro Sampaio 2019-04-04 01:02:30 UTC

Created wireshark tracking bugs for this issue:

Affects: fedora-all [bug 1695977]