WiresharkApplication
CVE-2024-11595
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 · uneditedFiveCo RAP dissector infinite loop in Wireshark 4.4.0 to 4.4.1 and 4.2.0 to 4.2.8 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 confidenceThe FiveCo RAP dissector in Wireshark contains an infinite loop vulnerability that can be triggered by processing malicious packets or crafted capture files, causing the application to hang 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
>= 4.2.0, < 4.2.9>= 4.4.0, < 4.4.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Wireshark versionRun 'wireshark --version' or 'tshark --version' to determine the exact version number installedAffected if Version is >= 4.2.0 and < 4.2.9, or >= 4.4.0 and < 4.4.2
-
Verify FiveCo RAP dissector is presentCheck if the dissector exists in the Wireshark installation by looking for 'epan/dissectors/packet-fiveco_rap.c' in the source or checking dissector availability in the GUI under Analyze > Enabled ProtocolsAffected if The FiveCo RAP dissector is enabled in the Wireshark installation
-
Identify capture files or packet streams containing FiveCo RAP trafficReview capture files (.pcap, .pcapng) or network traffic for the presence of FiveCo RAP protocol packets, which can be identified in Wireshark by filtering for 'fiverap' or similar FiveCo-related protocolsAffected if Processing capture files or receiving live network traffic that contains FiveCo RAP protocol data
You are affected if Wireshark version falls within 4.2.0-4.2.8 or 4.4.0-4.4.1 AND you process capture files or receive packet streams containing FiveCo RAP protocol data.
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 · scoped4.2.94.4.2
Update Wireshark to a version beyond 4.4.1 or 4.2.8, and avoid opening untrusted capture files or receiving untrusted packet streams.
Wireshark 4.2.9 or later in the 4.2.x series, or 4.4.2 or later in the 4.4.x series
- 1. Check current Wireshark version via Help > About Wireshark or running 'wireshark --version'
- 2. Download Wireshark 4.2.9 or later (or 4.4.2 or later) from the official Wireshark website: https://www.wireshark.org/download.html
- 3. Uninstall the current Wireshark version
- 4. Install the newly downloaded fixed version
- 5. Verify the new version is installed by running 'wireshark --version'
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wireshark
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11595 — 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-2024-11595 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