CVE-2017-15192

high
Published 2017-10-10 ยท Modified 2026-05-13
CVSS v3
7.5
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS v4 NEW
โ€”
not yet in upstream
VIR risk
7.5

Description

In Wireshark 2.4.0 to 2.4.1 and 2.2.0 to 2.2.9, the BT ATT dissector could crash. This was addressed in epan/dissectors/packet-btatt.c by considering a case where not all of the BTATT packets have the same encapsulation level.

Predictions

Exploit likelihood
83%
Patch ETA
โ€”

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ€” if you've already worked around this in production โ€” publish your fix to the community-verified tier.

โœš Propose a mitigation on Community โ†’ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

OSVersionStatusFixed in
suse slesaffected
arch archfixed2.4.2-1
debian debianbookwormfixed2.4.2-1
debian debianbullseyefixed2.4.2-1
debian debianforkyfixed2.4.2-1
debian debiansidfixed2.4.2-1
debian debiantrixiefixed2.4.2-1

Application impact

VendorProductVersionsFixed
wiresharkwireshark2.2.0
wiresharkwireshark2.2.1
wiresharkwireshark2.2.2
wiresharkwireshark2.2.3
wiresharkwireshark2.2.4
wiresharkwireshark2.2.5
wiresharkwireshark2.2.6
wiresharkwireshark2.2.7
wiresharkwireshark2.2.8
wiresharkwireshark2.2.9
wiresharkwireshark2.4.0
wiresharkwireshark2.4.1

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.