Bug 1697952 (CVE-2019-10900)

Summary: CVE-2019-10900 wireshark: Rbm dissector infinite loop (wnpa-sec-2019-13)
Product: [Other] Security Response Reporter: Marian Rehak <mrehak>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: denis, huzaifas, lemenkov, mruprich, msehnout, phatina, rvokal, sergey.avseyev
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: wireshark 3.0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-16 08:05:29 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: 1697953    
Bug Blocks: 1697993    

Description Marian Rehak 2019-04-09 11:00:03 UTC
It may be possible to make Wireshark consume excessive CPU resources by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file. 

External Referencies:
https://www.wireshark.org/security/wnpa-sec-2019-13.html

Upstream bug(s):
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15612

Comment 1 Marian Rehak 2019-04-09 11:00:12 UTC
Created wireshark tracking bugs for this issue:

Affects: fedora-all [bug 1697953]

Comment 3 Riccardo Schirone 2019-05-15 15:30:35 UTC
Statement:

This issue did not affect the versions of wireshark as shipped with Red Hat Enterprise Linux 8 as they did not include support for Ruby Marshal Object (RBM).

Comment 4 Riccardo Schirone 2019-05-16 09:42:51 UTC
An infinite loop in the Rbm dissector is possible when a malformed packet is read on the wire or analyzed from a trace file.

Comment 5 Riccardo Schirone 2019-05-16 09:42:53 UTC
External References:

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