WiresharkApplication
CVE-2025-9817
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 · uneditedSSH dissector crash in Wireshark 4.4.0 to 4.4.8 allows denial of service
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 confidenceThe SSH protocol dissector in Wireshark versions 4.4.0 through 4.4.8 contains a flaw that causes a crash when processing specially crafted SSH network traffic, enabling a remote denial of service condition.
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
>= 4.4.0, <= 4.4.8= 4.4.9CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Wireshark versionRun 'wireshark --version' from command line, or open Wireshark and go to Help > About Wireshark to view the version numberAffected if The version is 4.4.0 through 4.4.8, or exactly 4.4.9
-
Confirm SSH dissector is activeOpen Wireshark, go to Analyze > Enabled Protocols, and verify that SSH protocol is enabled (it is enabled by default)Affected if SSH protocol is enabled in the protocol settings
-
Identify capture source for SSH trafficCheck if Wireshark is capturing live network traffic or processing pcap files that may contain SSH trafficAffected if Wireshark is actively parsing SSH protocol data from network captures or saved capture files
You are affected if Wireshark version is between 4.4.0 and 4.4.8 inclusive, or exactly 4.4.9, and the SSH dissector is enabled and processing SSH traffic.
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 · scopedUpgrade Wireshark to version 4.4.9 or later to obtain the patched SSH dissector.
Wireshark 4.4.10 or later
- 1. Verify current Wireshark version by running: wireshark --version
- 2. Download the latest stable Wireshark release (4.4.10 or later) from the official Wireshark website: https://www.wireshark.org/download.html
- 3. Uninstall the current Wireshark installation
- 4. Install the downloaded version (4.4.10 or later)
- 5. Verify the installation was successful by running: wireshark --version
- 6. Test that the SSH dissector loads properly with a sample capture file
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wireshark
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9817 — 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-2025-9817 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