Bug 2138742 (CVE-2022-3725)

Summary: CVE-2022-3725 wireshark: OPUS dissector crash
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: mruprich
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: wireshark 3.6.9 Doc Type: If docs needed, set a value
Doc Text:
A vulnerability was found in Wireshark. This flaw causes a crash in the OPUS protocol dissector in Wireshark, leading to a denial of service via packet injection or a crafted capture file.
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-02 23:03:16 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: 2138744    
Bug Blocks: 2138401    

Description Sandipan Roy 2022-10-31 05:22:40 UTC
In dissect_opus() at wireshark-3.6.8/epan/dissectors/packet-opus.c:254, frame_count is truncated below 0x3F (63) and checked if framesize * frame_count > 120 * MAX_FRAMES_COUNT. But when stack variable frames[MAX_FRAMES_COUNT] is indexed with frame_count later, we didn't make sure frame_count won't excess MAX_FRAMES_COUNT, leading to stack-over-flow write when the begin/size values are put into frames later.
This flaw affects the current released stable wireshark/tshark/... on Linux/Windows/Mac/..., previous versions may also be affected. This issue hasn't been reported elsewhere.

https://gitlab.com/wireshark/wireshark/-/issues/18378
https://www.wireshark.org/security/wnpa-sec-2022-07 - OPUS dissector crash. Issue 18378.

Comment 1 Sandipan Roy 2022-10-31 05:26:42 UTC
Created wireshark tracking bugs for this issue:

Affects: fedora-all [bug 2138744]

Comment 2 Product Security DevOps Team 2022-12-02 23:03:15 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2022-3725