WiresharkApplication
CVE-2022-4345
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInfinite loops in the BPv6, OpenFlow, and Kafka protocol dissectors in Wireshark 4.0.0 to 4.0.1 and 3.6.0 to 3.6.9 allows denial of service via packet injection or crafted capture file
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceWireshark contains protocol dissectors for BPv6, OpenFlow, and Kafka that are vulnerable to infinite loops when processing specially crafted packets or capture files. An attacker can inject malicious packets or provide a crafted capture file to trigger the infinite loop, causing Wireshark to become unresponsive and resulting in denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
WiresharkApplication
>= 3.6.0, < 3.6.10>= 4.0.0, < 4.0.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Wireshark is installed and get its versionRun 'wireshark --version' or 'tshark --version' on the command line to obtain the installed Wireshark version numberAffected if The version shown is greater than or equal to 3.6.0 but less than 3.6.10, or greater than or equal to 4.0.0 but less than 4.0.2
-
Confirm Wireshark installation path (optional)On Linux, run 'which wireshark' or 'dpkg -l | grep wireshark'; on Windows, check Program Files folder or run 'where wireshark'Affected if Wireshark is found and the version matches the affected ranges from step 1
-
Identify if BPv6, OpenFlow, or Kafka dissectors are availableOpen Wireshark and go to Help > About > Plugins, or check the plugins folder for dissectors. These protocols are typically built-in dissectors included with Wireshark.Affected if The dissectors for BPv6, OpenFlow, or Kafka are present in the installation (they are included by default in affected versions)
You are affected if Wireshark is installed with a version in the range 3.6.0 through 3.6.9, or 4.0.0 through 4.0.1, since these versions contain the vulnerable BPv6, OpenFlow, and Kafka protocol dissectors that can trigger infinite loops.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.6.104.0.2
Update Wireshark to version 4.0.2 or later (for the 4.x branch) or version 3.6.10 or later (for the 3.6.x branch) to obtain patches for the infinite loop vulnerabilities in the affected protocol dissectors.
Wireshark 3.6.10 or later in the 3.6.x branch, or 4.0.2 or later in the 4.0.x branch
- Check current Wireshark version: tshark -v or wireshark -v
- Back up any existing capture files and custom profiles
- For Debian/Ubuntu: sudo apt-get update && sudo apt-get install wireshark
- For Fedora/RHEL: sudo dnf update wireshark
- For macOS: brew upgrade wireshark or download from https://www.wireshark.org/download.html
- For Windows: download installer from https://www.wireshark.org/download.html and run update
- Verify fixed version is installed: tshark -v (should show 3.6.10 or later, or 4.0.2 or later)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wireshark
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-4345 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-4345 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data