LiveActive security incident?Get immediate response
CVE Record

CVE-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.

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue could make affected Wireshark versions crash while decoding Bluetooth L2CAP data. It is a reliability and analyst-workstation risk, not evidence of system takeover. Business urgency is mainly for teams that inspect packet captures, especially untrusted captures or Bluetooth traffic.

Executive priority

Treat as a moderate operational fix for packet-analysis environments. Prioritize security teams and labs first, because crashes during analysis can disrupt investigations and may be triggered by untrusted captures.

Technical view

Wireshark 2.2.0 through 2.2.6 and 2.0.0 through 2.0.12 had a divide-by-zero flaw in the Bluetooth L2CAP dissector. The described fix validates an interval value in packet-btl2cap.c. No CVSS, CWE, or KEV entry is provided in the bundle.

Likely exposure

Exposure is most likely on security, network, QA, or support workstations running the affected Wireshark versions and opening packet captures containing Bluetooth L2CAP data. Server-side exposure is not indicated by the supplied sources.

Exploitation context

The bundle does not show active exploitation, and KEV is false. Public references include Wireshark advisory material, bug tracking, OSS-Fuzz, vulnerability databases, a code commit, and a Debian LTS update, but no source here proves in-the-wild abuse.

Researcher notes

The vulnerable component is the Bluetooth L2CAP dissector. The source bundle says the issue was fixed by validating an interval value in epan/dissectors/packet-btl2cap.c. Details are insufficient here to assign a precise exploitability rating beyond crash-oriented denial of service.

Mitigation direction

  • Upgrade Wireshark beyond the affected 2.2.x and 2.0.x ranges using vendor or distro guidance.
  • Apply relevant Debian or operating system security updates where Wireshark is packaged.
  • Avoid opening untrusted Bluetooth packet captures on affected Wireshark versions.
  • Use isolated analysis workstations for suspicious captures until tools are updated.

Validation and detection

  • Inventory installed Wireshark versions on analyst and engineering workstations.
  • Check for Wireshark 2.2.0-2.2.6 or 2.0.0-2.0.12.
  • Confirm package manager or application inventory shows an updated Wireshark build.
  • Review packet-analysis workflows for use of untrusted Bluetooth captures.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-9344 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.