Bug 2054047 (CVE-2022-0586) - CVE-2022-0586 wireshark: RTMPT dissector infinite loop
Summary: CVE-2022-0586 wireshark: RTMPT dissector infinite loop
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2022-0586
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: 2054048
Blocks: 2054060
TreeView+ depends on / blocked
 
Reported: 2022-02-14 06:07 UTC by Sandipan Roy
Modified: 2022-04-10 16:08 UTC (History)
8 users (show)

Fixed In Version: wireshark 3.6.2, wireshark 3.4.12
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-10 16:07:38 UTC


Attachments (Terms of Use)

Description Sandipan Roy 2022-02-14 06:07:02 UTC
It was discovered that in Wireshark before 3.6.2 (and 3.4.12) the RTMPT dissector could go into an infinite loop. 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.

Affected versions: 3.6.0 to 3.6.1, 3.4.0 to 3.4.11
Fixed versions: 3.6.2, 3.4.12 

References:
https://www.wireshark.org/security/wnpa-sec-2022-01
https://gitlab.com/wireshark/wireshark/-/issues/17813

Comment 1 Sandipan Roy 2022-02-14 06:07:30 UTC
Created wireshark tracking bugs for this issue:

Affects: fedora-all [bug 2054048]

Comment 2 devthomp 2022-04-10 16:07:38 UTC
In reply to comment #0:
> It was discovered that in Wireshark before 3.6.2 (and 3.4.12) the RTMPT
> dissector could go into an infinite loop. 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.
> 
> Affected versions: 3.6.0 to 3.6.1, 3.4.0 to 3.4.11
> Fixed versions: 3.6.2, 3.4.12 
> 
> References:
> https://www.wireshark.org/security/wnpa-sec-2022-01
> https://gitlab.com/wireshark/wireshark/-/issues/17813

Marking not affected given our rhel wireshark release versions:

enterprise_linux:8.1:appstream/wireshark-2.6.2-11.el8
enterprise_linux:8.2:appstream/wireshark-2.6.2-12.el8
enterprise_linux:8.4:appstream/wireshark-2.6.2-12.el8
enterprise_linux:8.5:appstream/wireshark-2.6.2-14.el8
enterprise_linux:9.0:appstream/wireshark-3.4.10-1.el9


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