Bug 1697952 (CVE-2019-10900) - CVE-2019-10900 wireshark: Rbm dissector infinite loop (wnpa-sec-2019-13)
Summary: CVE-2019-10900 wireshark: Rbm dissector infinite loop (wnpa-sec-2019-13)
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2019-10900
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: 1697953
Blocks: Embargoed1697993
TreeView+ depends on / blocked
 
Reported: 2019-04-09 11:00 UTC by Marian Rehak
Modified: 2021-02-16 22:07 UTC (History)
8 users (show)

Fixed In Version: wireshark 3.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-16 08:05:29 UTC

Attachments (Terms of Use)

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 2 Riccardo Schirone 2019-05-15 15:28:14 UTC 
Upstream patch:
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=f273ecd5d94f0c39d1683ed147656daee3ef799b
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
Note You need to log in before you can comment on or make changes to this bug.