Bug 2054049 (CVE-2022-0585)

Summary: CVE-2022-0585 wireshark: Large loops in multiple dissectors
Product: [Other] Security Response Reporter: Sandipan Roy <saroy>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: alekcejk, denis, huzaifas, lemenkov, mruprich, peter, rvokal, sergey.avseyev
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: wireshark 3.6.2, wireshark 3.4.12 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-10 16:15: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: 2054050    
Bug Blocks: 2054060    

Description Sandipan Roy 2022-02-14 06:10:52 UTC
It was discovered that Wireshark before 3.6.2, 3.4.12 there are large loops in multiple dissectors, including AMP, ATN-ULCS and possibly other ASN.1 PER dissectors, BP, GDSDB, OpenFlow v5, P_MUL, SoulSeek, TDS, WBXML, WSP and possibly other WAP dissectors, and ZigBee ZCL. 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-02
https://gitlab.com/wireshark/wireshark/-/issues/17829
https://gitlab.com/wireshark/wireshark/-/issues/17842
https://gitlab.com/wireshark/wireshark/-/issues/17847
https://gitlab.com/wireshark/wireshark/-/issues/17855
https://gitlab.com/wireshark/wireshark/-/issues/17891
https://gitlab.com/wireshark/wireshark/-/issues/17925
https://gitlab.com/wireshark/wireshark/-/issues/17926
https://gitlab.com/wireshark/wireshark/-/issues/17931
https://gitlab.com/wireshark/wireshark/-/issues/17932
https://gitlab.com/wireshark/wireshark/-/issues/17933

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

Affects: fedora-all [bug 2054050]

Comment 2 devthomp 2022-04-10 16:15:29 UTC
In reply to comment #0:
> It was discovered that Wireshark before 3.6.2, 3.4.12 there are large loops
> in multiple dissectors, including AMP, ATN-ULCS and possibly other ASN.1 PER
> dissectors, BP, GDSDB, OpenFlow v5, P_MUL, SoulSeek, TDS, WBXML, WSP and
> possibly other WAP dissectors, and ZigBee ZCL. 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-02
> https://gitlab.com/wireshark/wireshark/-/issues/17829
> https://gitlab.com/wireshark/wireshark/-/issues/17842
> https://gitlab.com/wireshark/wireshark/-/issues/17847
> https://gitlab.com/wireshark/wireshark/-/issues/17855
> https://gitlab.com/wireshark/wireshark/-/issues/17891
> https://gitlab.com/wireshark/wireshark/-/issues/17925
> https://gitlab.com/wireshark/wireshark/-/issues/17926
> https://gitlab.com/wireshark/wireshark/-/issues/17931
> https://gitlab.com/wireshark/wireshark/-/issues/17932
> https://gitlab.com/wireshark/wireshark/-/issues/17933

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