CVE-2017-9344
published 2017-06-02CVE-2017-9344: In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the Bluetooth L2CAP dissector could divide by zero. This was addressed in epan/dissectors/packet-btl2cap.c by…
PriorityP335high7.5CVSS 3.0
AVNACLPRNUINSUCNINAH
EPSS
2.72%
84.5th percentile
In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the Bluetooth L2CAP dissector could divide by zero. This was addressed in epan/dissectors/packet-btl2cap.c by validating an interval value.
Affected
8 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | wireshark | < wireshark 2.2.7-1 (bookworm) | wireshark 2.2.7-1 (bookworm) |
| wireshark | wireshark | >= 0 < 2.2.7-1 | 2.2.7-1 |
| wireshark | wireshark | >= 0 < 2.2.7-1 | 2.2.7-1 |
| wireshark | wireshark | >= 0 < 2.2.7-1 | 2.2.7-1 |
| wireshark | wireshark | >= 0 < 2.2.7-1 | 2.2.7-1 |
| wireshark | wireshark | 2.0.0 – 2.0.12 | — |
| wireshark | wireshark | 2.2.0 – 2.2.6 | — |
CVSS provenance
nvdv3.07.5HIGHCVSS:3.0/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.5LOW
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-fp6q-4pvx-cxr2: In Wireshark 2
ghsa_unreviewed·2022-05-14
CVE-2017-9344 [HIGH] CWE-369 GHSA-fp6q-4pvx-cxr2: In Wireshark 2
In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the Bluetooth L2CAP dissector could divide by zero. This was addressed in epan/dissectors/packet-btl2cap.c by validating an interval value.
OSV
CVE-2017-9344: In Wireshark 2
osv·2017-06-02·CVSS 7.5
CVE-2017-9344 [HIGH] CVE-2017-9344: In Wireshark 2
In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the Bluetooth L2CAP dissector could divide by zero. This was addressed in epan/dissectors/packet-btl2cap.c by validating an interval value.
Red Hat
wireshark: BT L2CAP dissector divide by zero (wnpa-sec-2017-29)
vendor_redhat·2017-06-01·CVSS 7.5
CVE-2017-9344 [HIGH] wireshark: BT L2CAP dissector divide by zero (wnpa-sec-2017-29)
wireshark: BT L2CAP dissector divide by zero (wnpa-sec-2017-29)
In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the Bluetooth L2CAP dissector could divide by zero. This was addressed in epan/dissectors/packet-btl2cap.c by validating an interval value.
Package: wireshark (Red Hat Enterprise Linux 6) - Will not fix
Package: wireshark (Red Hat Enterprise Linux 7) - Will not fix
Debian
CVE-2017-9344: wireshark - In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the Bluetooth L2CAP dissector c...
vendor_debian·2017·CVSS 7.5
CVE-2017-9344 [HIGH] CVE-2017-9344: wireshark - In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the Bluetooth L2CAP dissector c...
In Wireshark 2.2.0 to 2.2.6 and 2.0.0 to 2.0.12, the Bluetooth L2CAP dissector could divide by zero. This was addressed in epan/dissectors/packet-btl2cap.c by validating an interval value.
Scope: local
bookworm: resolved (fixed in 2.2.7-1)
bullseye: resolved (fixed in 2.2.7-1)
forky: resolved (fixed in 2.2.7-1)
sid: resolved (fixed in 2.2.7-1)
trixie: resolved (fixed in 2.2.7-1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2017-9344 wireshark: BT L2CAP dissector divide by zero (wnpa-sec-2017-29)
bugzilla·2017-06-02·CVSS 7.5
CVE-2017-9344 [HIGH] CVE-2017-9344 wireshark: BT L2CAP dissector divide by zero (wnpa-sec-2017-29)
CVE-2017-9344 wireshark: BT L2CAP dissector divide by zero (wnpa-sec-2017-29)
It was reported that Wireshark could crash. It may be possible to make Wireshark crash by injecting a malformed packet onto the wire or by convincing someone to read a malformed packet trace file.
Upstream bug(s):
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13701
External References:
https://www.wireshark.org/security/wnpa-sec-2017-29.html
Discussion:
Created wireshark tracking bugs for this issue:
Affects: fedora-all [bug 1458149]
Bugzilla
CVE-2017-11411 CVE-2017-9343 CVE-2017-9344 CVE-2017-9345 CVE-2017-9346 CVE-2017-9347 CVE-2017-9348 CVE-2017-9349 CVE-2017-9350 CVE-2017-9351 CVE-2017-9352 CVE-2017-9353 CVE-2017-9354 wireshark: variou
bugzilla·2017-06-02·CVSS 7.5
CVE-2017-11411 [HIGH] CVE-2017-11411 CVE-2017-9343 CVE-2017-9344 CVE-2017-9345 CVE-2017-9346 CVE-2017-9347 CVE-2017-9348 CVE-2017-9349 CVE-2017-9350 CVE-2017-9351 CVE-2017-9352 CVE-2017-9353 CVE-2017-9354 wireshark: variou
CVE-2017-11411 CVE-2017-9343 CVE-2017-9344 CVE-2017-9345 CVE-2017-9346 CVE-2017-9347 CVE-2017-9348 CVE-2017-9349 CVE-2017-9350 CVE-2017-9351 CVE-2017-9352 CVE-2017-9353 CVE-2017-9354 wireshark: various flaws [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.
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 als
http://www.securityfocus.com/bid/98796http://www.securitytracker.com/id/1038612https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=1539https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13701https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=6308ae03d82a29a2e3d75e1c325c8a9f6c44dcdfhttps://lists.debian.org/debian-lts-announce/2019/03/msg00031.htmlhttps://www.wireshark.org/security/wnpa-sec-2017-29.htmlhttp://www.securityfocus.com/bid/98796http://www.securitytracker.com/id/1038612https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=1539https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13701https://code.wireshark.org/review/gitweb?p=wireshark.git%3Ba=commit%3Bh=6308ae03d82a29a2e3d75e1c325c8a9f6c44dcdfhttps://lists.debian.org/debian-lts-announce/2019/03/msg00031.htmlhttps://www.wireshark.org/security/wnpa-sec-2017-29.html
2017-06-02
Published