dbcve.org
WiresharkApplication

CVE-2022-3724

HIGH · 7.5 CVSS v3.1 Published 2022-12-09
Fix available
A fix is available. Upgrade to after 3.6.8 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Crash in the USB HID protocol dissector in Wireshark 3.6.0 to 3.6.8 allows denial of service via packet injection or crafted capture file on Windows

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 confidence

A crash vulnerability exists in the USB HID protocol dissector of Wireshark versions 3.6.0 through 3.6.8. The vulnerability can be triggered via injection of malicious packets or by opening a crafted capture file, specifically on Windows systems, resulting in denial of service.

MitigationUpgrade Wireshark to version 3.6.9 or later. Until upgraded, avoid opening capture files from untrusted sources or monitoring traffic on untrusted networks on Windows systems.

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
Affected:>= 3.6.0, <= 3.6.8

CVSS 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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Wireshark installation
    Open a command prompt and run 'wireshark --version' or open Wireshark and go to Help > About Wireshark to view the version number
    Affected if No version output is returned or Wireshark is not installed (not affected)
  2. Confirm the installed version falls within the affected range
    Compare the version number from step 1 against the affected range: versions 3.6.0 through 3.6.8 inclusive
    Affected if The installed version is 3.6.0, 3.6.1, 3.6.2, 3.6.3, 3.6.4, 3.6.5, 3.6.6, 3.6.7, or 3.6.8
  3. Verify the operating system is Windows
    Check the system type by running 'systeminfo | findstr /B /C:"OS Name"' or inspecting system properties
    Affected if The system is running Windows (the vulnerability specifically affects Windows systems)
  4. Confirm USB HID dissector is active
    In Wireshark, go to Analyze > Enabled Protocols and verify 'usbhid' is enabled, or check if USB HID traffic has been dissected in any recent capture files
    Affected if The USB HID protocol dissector is enabled and available for processing capture files

The environment is affected if Wireshark versions 3.6.0 through 3.6.8 are installed on a Windows system with the USB HID dissector enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 3.6.8
Interim mitigation

Upgrade Wireshark to version 3.6.9 or later. Until upgraded, avoid opening capture files from untrusted sources or monitoring traffic on untrusted networks on Windows systems.

Recommended fix Moderate confidence

Wireshark 3.6.9 or later (latest stable 3.6.x release)

  1. 1. Determine your current Wireshark version by opening Wireshark and going to Help > About Wireshark, or by running 'wireshark --version' from command line
  2. 2. If running version 3.6.0 through 3.6.8, plan for upgrade
  3. 3. Download Wireshark from the official website (www.wireshark.org) - obtain the latest stable release (version 3.6.9 or later)
  4. 4. Close Wireshark if currently running
  5. 5. Install the new version, ensuring you back up any custom profiles or configurations if desired
  6. 6. Verify the new version is installed by checking Help > About Wireshark
  7. 7. Test opening the USB HID dissector with a sample capture file to confirm functionality
Caveat Minor: Review release notes for any configuration or behavior changes between 3.6.8 and the target upgrade version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wireshark Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3724 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-3724 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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