CVE-2020-26575
published 2020-10-06CVE-2020-26575: In Wireshark through 3.2.7, the Facebook Zero Protocol (aka FBZERO) dissector could enter an infinite loop. This was addressed in…
PriorityP338high7.5CVSS 3.1
AVNACLPRNUINSUCNINAH
EPSS
3.12%
86.4th percentile
In Wireshark through 3.2.7, the Facebook Zero Protocol (aka FBZERO) dissector could enter an infinite loop. This was addressed in epan/dissectors/packet-fbzero.c by correcting the implementation of offset advancement.
Affected
10 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | wireshark | < wireshark 3.2.8-0.1 (bookworm) | wireshark 3.2.8-0.1 (bookworm) |
| fedoraproject | fedora | — | — |
| fedoraproject | fedora | — | — |
| oracle | zfs_storage_appliance_firmware | — | — |
| wireshark | wireshark | <= 3.2.7 | — |
| wireshark | wireshark | >= 0 < 3.2.8-0.1 | 3.2.8-0.1 |
| wireshark | wireshark | >= 0 < 3.2.8-0.1 | 3.2.8-0.1 |
| wireshark | wireshark | >= 0 < 3.2.8-0.1 | 3.2.8-0.1 |
| wireshark | wireshark | >= 0 < 3.2.8-0.1 | 3.2.8-0.1 |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:N/A:P
osv7.5HIGH
vendor_debian7.5HIGH
vendor_redhat7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-vw2j-3xrw-2q58: In Wireshark through 3
ghsa_unreviewed·2022-05-24
CVE-2020-26575 [HIGH] CWE-835 GHSA-vw2j-3xrw-2q58: In Wireshark through 3
In Wireshark through 3.2.7, the Facebook Zero Protocol (aka FBZERO) dissector could enter an infinite loop. This was addressed in epan/dissectors/packet-fbzero.c by correcting the implementation of offset advancement.
OSV
CVE-2020-26575: In Wireshark through 3
osv·2020-10-06·CVSS 7.5
CVE-2020-26575 [HIGH] CVE-2020-26575: In Wireshark through 3
In Wireshark through 3.2.7, the Facebook Zero Protocol (aka FBZERO) dissector could enter an infinite loop. This was addressed in epan/dissectors/packet-fbzero.c by correcting the implementation of offset advancement.
Red Hat
wireshark: FBZERO dissector could enter an infinite loop
vendor_redhat·2020-10-06·CVSS 7.5
CVE-2020-26575 [HIGH] CWE-835 wireshark: FBZERO dissector could enter an infinite loop
wireshark: FBZERO dissector could enter an infinite loop
In Wireshark through 3.2.7, the Facebook Zero Protocol (aka FBZERO) dissector could enter an infinite loop. This was addressed in epan/dissectors/packet-fbzero.c by correcting the implementation of offset advancement.
Statement: Wireshark as shipped with Red Hat Enterprise Linux 5, 6, and 7 is not affected by this flaw because the Facebook Zero Dissector was not yet introduced until version 2.4.0rc0.
Package: wireshark (Red Hat Enterprise Linux 5) - Not affected
Package: wireshark (Red Hat Enterprise Linux 6) - Not affected
Package: wireshark (Red Hat Enterprise Linux 7) - Not affected
Package: wireshark (Red Hat Enterprise Linux 8) - Will not fix
Debian
CVE-2020-26575: wireshark - In Wireshark through 3.2.7, the Facebook Zero Protocol (aka FBZERO) dissector co...
vendor_debian·2020·CVSS 7.5
CVE-2020-26575 [HIGH] CVE-2020-26575: wireshark - In Wireshark through 3.2.7, the Facebook Zero Protocol (aka FBZERO) dissector co...
In Wireshark through 3.2.7, the Facebook Zero Protocol (aka FBZERO) dissector could enter an infinite loop. This was addressed in epan/dissectors/packet-fbzero.c by correcting the implementation of offset advancement.
Scope: local
bookworm: resolved (fixed in 3.2.8-0.1)
bullseye: resolved (fixed in 3.2.8-0.1)
forky: resolved (fixed in 3.2.8-0.1)
sid: resolved (fixed in 3.2.8-0.1)
trixie: resolved (fixed in 3.2.8-0.1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2020-26575 wireshark: FBZERO dissector could enter an infinite loop
bugzilla·2020-10-07·CVSS 7.5
CVE-2020-26575 [HIGH] CVE-2020-26575 wireshark: FBZERO dissector could enter an infinite loop
CVE-2020-26575 wireshark: FBZERO dissector could enter an infinite loop
In Wireshark through 3.2.7, the Facebook Zero Protocol (aka FBZERO) dissector could enter an infinite loop. This was addressed in epan/dissectors/packet-fbzero.c by correcting the implementation of offset advancement.
References:
https://gitlab.com/wireshark/wireshark/-/commit/3ff940652962c099b73ae3233322b8697b0d10ab
https://gitlab.com/wireshark/wireshark/-/merge_requests/467
https://gitlab.com/wireshark/wireshark/-/merge_requests/471
https://gitlab.com/wireshark/wireshark/-/merge_requests/472
https://gitlab.com/wireshark/wireshark/-/merge_requests/473
Discussion:
Created wireshark tracking bugs for this issue:
Affects: fedora-all [bug 1886048]
---
Statement:
Wireshark as shipped with Red Hat Enterprise Linux
Bugzilla
CVE-2020-26575 wireshark: FBZERO dissector could enter an infinite loop [fedora-all]
bugzilla·2020-10-07·CVSS 7.5
CVE-2020-26575 [HIGH] CVE-2020-26575 wireshark: FBZERO dissector could enter an infinite loop [fedora-all]
CVE-2020-26575 wireshark: FBZERO dissector could enter an infinite loop [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported v
https://gitlab.com/wireshark/wireshark/-/commit/3ff940652962c099b73ae3233322b8697b0d10abhttps://gitlab.com/wireshark/wireshark/-/issues/16887https://gitlab.com/wireshark/wireshark/-/merge_requests/467https://gitlab.com/wireshark/wireshark/-/merge_requests/471https://gitlab.com/wireshark/wireshark/-/merge_requests/472https://gitlab.com/wireshark/wireshark/-/merge_requests/473https://lists.debian.org/debian-lts-announce/2021/02/msg00008.htmlhttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UHZSVK7PO2LTGFQXFHFXY6SOMSQ7UPRS/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/V2667E6WKVE56G66BVBVD7LJPIDOJ7K3/https://security.gentoo.org/glsa/202011-08https://www.oracle.com/security-alerts/cpujan2021.htmlhttps://www.wireshark.org/security/wnpa-sec-2020-14.htmlhttps://gitlab.com/wireshark/wireshark/-/commit/3ff940652962c099b73ae3233322b8697b0d10abhttps://gitlab.com/wireshark/wireshark/-/issues/16887https://gitlab.com/wireshark/wireshark/-/merge_requests/467https://gitlab.com/wireshark/wireshark/-/merge_requests/471https://gitlab.com/wireshark/wireshark/-/merge_requests/472https://gitlab.com/wireshark/wireshark/-/merge_requests/473https://lists.debian.org/debian-lts-announce/2021/02/msg00008.htmlhttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UHZSVK7PO2LTGFQXFHFXY6SOMSQ7UPRS/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/V2667E6WKVE56G66BVBVD7LJPIDOJ7K3/https://security.gentoo.org/glsa/202011-08https://www.oracle.com/security-alerts/cpujan2021.htmlhttps://www.wireshark.org/security/wnpa-sec-2020-14.html
2020-10-06
Published