FedoraOperating system · Fedoraproject
CVE-2024-4854
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 · uneditedMONGO and ZigBee TLV dissector infinite loops in Wireshark 4.2.0 to 4.2.4, 4.0.0 to 4.0.14, and 3.6.0 to 3.6.22 allow 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 infinite loops in the MONGO and ZigBee TLV dissectors. By crafting malicious packets or capture files with specially constructed TLV (Type-Length-Value) data, an attacker can cause Wireshark to enter an infinite loop, resulting in denial of service through resource exhaustion.
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
FedoraOperating system
= 39= 40
WiresharkApplication
>= 3.6.0, <= 3.6.22>= 4.0.0, <= 4.0.14>= 4.2.0, <= 4.2.4CVSS 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.
-
Check installed Wireshark versionRun 'wireshark --version' or 'tshark --version' to display the version numberAffected if The version displayed is 3.6.0 through 3.6.22, 4.0.0 through 4.0.14, or 4.2.0 through 4.2.4
-
Verify Wireshark is being used to dissect network trafficConfirm that Wireshark or TShark is actively processing capture files or capturing live network traffic that may contain MONGO or ZigBee protocolsAffected if Wireshark is actively processing capture files or live traffic containing MONGO or ZigBee protocol data
-
Check if dissectors are loadedOpen Wireshark, go to Help > About Wireshark > Plugins or folders, and verify that the TLV dissectors for MONGO and ZigBee are presentAffected if The MONGO and ZigBee dissectors are loaded and available in the Wireshark installation
A user is affected if they are running Wireshark versions 3.6.0-3.6.22, 4.0.0-4.0.14, or 4.2.0-4.2.4 and processing capture files or live traffic containing MONGO or ZigBee TLV 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 · scopedUpdate Wireshark to version 4.2.5, 4.0.15, or 3.6.23 or later. Avoid opening untrusted packet capture files or processing untrusted network traffic until the update is applied.
Wireshark 4.4.x or later (minimum fixed: 3.6.23, 4.0.15, or 4.2.5)
- 1. Check current Wireshark version by running: wireshark --version
- 2. If using a package manager (dnf/apt), update to the latest available version: sudo dnf update wireshark (Fedora) or sudo apt update && sudo apt upgrade wireshark (Debian)
- 3. Alternatively, download the latest stable Wireshark from the official website: https://www.wireshark.org/download.html
- 4. After updating, verify the new version is outside the affected ranges (3.6.0-3.6.22, 4.0.0-4.0.14, 4.2.0-4.2.4)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fedora
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-2024-4854 — 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-4854 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