Bug 1901990 - wireshark: the GQUIC dissector could crash due to incorrect offset advancement leading to excessive allocated memory
Summary: wireshark: the GQUIC dissector could crash due to incorrect offset advancemen...
Keywords:
Status: CLOSED DUPLICATE of bug 1893110
Alias: None
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1901991 1902055
Blocks: 1901992
TreeView+ depends on / blocked
 
Reported: 2020-11-26 14:46 UTC by Marian Rehak
Modified: 2021-02-16 18:49 UTC (History)
10 users (show)

Fixed In Version: wireshark 3.4.0, wireshark 3.2.8
Doc Type: If docs needed, set a value
Doc Text:
An uncontrolled resource consumption flaw was discovered in wireshark, in its GQUIC dissector. A remote attacker could use this flaw to crash a running instance of wireshark/tshark or prevent it from reading a saved PCAP file.
Clone Of:
Environment:
Last Closed: 2020-11-30 15:41:06 UTC
Embargoed:

Attachments (Terms of Use)

Description Marian Rehak 2020-11-26 14:46:49 UTC 
In Wireshark 3.2.0 to 3.2.7, the GQUIC dissector could crash. This was addressed in epan/dissectors/packet-gquic.c by correcting the implementation of offset advancement.

Upstream Issue:

https://gitlab.com/wireshark/wireshark/-/issues/16897

Upstream patch:

https://gitlab.com/wireshark/wireshark/-/commit/b287e7165e8aa89cde6ae37e7c257c5d87d16b9b

External Reference:

https://www.wireshark.org/security/wnpa-sec-2020-15.html
Comment 1 Marian Rehak 2020-11-26 14:47:16 UTC 
Created wireshark tracking bugs for this issue:

Affects: fedora-all [bug 1901991]
Comment 3 Riccardo Schirone 2020-11-30 15:41:06 UTC 
This is actually the same flaw bug as bug 1893110. See that instead.

*** This bug has been marked as a duplicate of bug 1893110 ***
Note You need to log in before you can comment on or make changes to this bug.