dbcve.org
WiresharkApplication

CVE-2018-7333

HIGH · 7.5 CVSS v3.0 Published 2018-02-23
Fix available
A fix is available. Upgrade to after 2.4.4 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
In Wireshark 2.4.0 to 2.4.4 and 2.2.0 to 2.2.12, epan/dissectors/packet-rpcrdma.c had an infinite loop that was addressed by validating a chunk size.

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

Wireshark's RPC RDMA dissector (packet-rpcrdma.c) contains an infinite loop vulnerability that can be triggered by specially crafted packet data. The vulnerability is exploited when malformed or malicious packets with invalid chunk sizes are processed, causing Wireshark to hang or become unresponsive.

MitigationUpgrade Wireshark to version 2.4.5 or later (for the 2.4.x branch) or version 2.2.13 or later (for the 2.2.x branch). Until upgrade is possible, avoid opening untrusted packet capture files from unknown sources.

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:>= 2.2.0, <= 2.2.12>= 2.4.0, <= 2.4.4

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.0/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 installed Wireshark version
    Run 'wireshark --version' or 'tshark --version' from command line, or open Wireshark and go to Help > About > Version
    Affected if Version is 2.2.0 through 2.2.12, or 2.4.0 through 2.4.4 (inclusive)
  2. Confirm RPC RDMA dissector is present
    Check that packet-rpcrdma.c dissector exists in the Wireshark installation; in Wireshark UI go to Analyze > Enabled Protocols and search for 'RDMA' or 'RPC RDMA'
    Affected if The RPC RDMA protocol dissector is enabled (it is typically enabled by default)
  3. Identify source of capture files
    Review recent packet capture files opened in Wireshark; check if they originate from untrusted or unknown sources
    Affected if You regularly open pcap files from unknown or untrusted sources, which could contain malicious RPC RDMA packets

You are affected if your Wireshark version falls within 2.2.0-2.2.12 or 2.4.0-2.4.4 and you process capture files that may contain RPC RDMA traffic with malformed chunk sizes.

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.

From vendor data
Upgrade available Upgrade to a release after 2.4.4
Interim mitigation

Upgrade Wireshark to version 2.4.5 or later (for the 2.4.x branch) or version 2.2.13 or later (for the 2.2.x branch). Until upgrade is possible, avoid opening untrusted packet capture files from unknown sources.

Fix this in Wireshark Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
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,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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