dbcve.org
WiresharkApplication

CVE-2024-8645

MEDIUM · 5.5 CVSS v3.1 Published 2024-09-10
Fix available
A fix is available. Upgrade to 4.0.16 / 4.2.6 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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
SPRT dissector crash in Wireshark 4.2.0 to 4.0.5 and 4.0.0 to 4.0.15 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 · moderate confidence

The SPRT protocol dissector in Wireshark contains a flaw that causes a crash when processing malformed SPRT packets. Attackers can trigger this by either injecting malicious packets onto a monitored network or enticing users to open a crafted capture file containing specially crafted SPRT data.

MitigationUpgrade to Wireshark 4.2.6, 4.0.16, or later versions. Until patched, avoid opening capture files from untrusted sources and exercise caution when processing live traffic on untrusted networks.

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:>= 4.0.0, < 4.0.16>= 4.2.0, < 4.2.6

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/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 checks

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

  1. Check installed Wireshark version
    Run 'wireshark --version' or 'tshark --version' from command line, or open Wireshark and go to Help > About Wireshark to view the version number
    Affected if The version is 4.0.0 through 4.0.15, or 4.2.0 through 4.2.5 (these fall within the vulnerable ranges)
  2. Confirm SPRT protocol support is present
    Open any capture file in Wireshark and check if SPRT appears in the list of dissectors (look for 'SPRT' in Analyze > Enabled Protocols, or attempt to filter by SPRT in the display filter field)
    Affected if SPRT dissector is present and enabled in the installation
  3. Identify SPRT traffic in recent captures
    Review any recent .pcap or .pcapng files for SPRT protocol usage by applying 'sprt' as a display filter, or monitor live captures for SPRT packets using the same filter
    Affected if SPRT packets are present in capture files or live traffic that has been or would be processed by Wireshark

You are affected if Wireshark version is 4.0.0-4.0.15 or 4.2.0-4.2.5 AND you process SPRT protocol traffic or open capture files containing SPRT packets.

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 4.0.16 / 4.2.6 or later
Fixed in 4.0.164.2.6
Interim mitigation

Upgrade to Wireshark 4.2.6, 4.0.16, or later versions. Until patched, avoid opening capture files from untrusted sources and exercise caution when processing live traffic on untrusted networks.

Recommended fix High confidence

Wireshark 4.0.16 or later for 4.0.x branch; Wireshark 4.2.6 or later for 4.2.x branch

  1. 1. Identify the currently installed Wireshark version using 'wireshark --version' or 'tshark --version'
  2. 2. If running Wireshark 4.0.x series (4.0.0 to 4.0.15), upgrade to version 4.0.16 or later
  3. 3. If running Wireshark 4.2.x series (4.2.0 to 4.2.5), upgrade to version 4.2.6 or later
  4. 4. For Debian-based systems, run 'sudo apt-get update && sudo apt-get install wireshark' to obtain the latest available version
  5. 5. For other systems, download the appropriate installer from https://www.wireshark.org/download.html
  6. 6. Verify the upgrade was successful by running 'wireshark --version' and confirming the new version number
Caveat Minor - this is a bug fix release; no breaking changes expected for typical users

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
5.0 hours of engineering $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 $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-8645 — 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-2024-8645 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