dbcve.org
WiresharkApplication

CVE-2007-3392

MEDIUM · 5.0 CVSS v2.0 Published 2007-06-26
Fix available
A fix is available. Upgrade to after 0.99.5 or later.
See remediation →
59/100
Remediation priority · Elevated
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
Wireshark before 0.99.6 allows remote attackers to cause a denial of service via malformed (1) SSL or (2) MMS packets that trigger an infinite loop.

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 versions prior to 0.99.6 contain an infinite loop vulnerability in the SSL and MMS protocol dissectors. When processing malformed SSL or MMS packets, the dissector enters an infinite loop, causing a denial of service by consuming CPU resources indefinitely.

MitigationUpgrade Wireshark to version 0.99.6 or later to patch the infinite loop vulnerability in the SSL and MMS dissectors.

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:<= 0.99.5

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
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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. Determine installed Wireshark version
    Run 'wireshark -v' or 'tshark -v' from command line, or check the application Help > About section in the GUI
    Affected if version number is 0.99.5 or lower (any version <= 0.99.5)
  2. Identify if SSL/TLS traffic is being captured or analyzed
    Inspect active capture filters or examine any pcap files currently open in Wireshark for SSL/TLS protocol traffic (typically port 443 or 'ssl' in the protocol column)
    Affected if SSL traffic is being dissected by Wireshark with a vulnerable version
  3. Identify if MMS traffic is being captured or analyzed
    Inspect capture filters or examine open pcap files for MMS protocol traffic (multimedia messaging service, typically port 80 or 8080 with MMS content)
    Affected if MMS traffic is being dissected by Wireshark with a vulnerable version
  4. Check for malformed packet processing
    Review any pcap files or live captures for packets that appear truncated, corrupted, or have unusual SSL/MMS header structures
    Affected if malformed SSL or MMS packets are present and being processed by a vulnerable Wireshark version

Environment is affected if Wireshark version is 0.99.5 or earlier AND SSL or MMS protocol dissectors are actively processing traffic (live captures or pcap files).

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 0.99.5
Interim mitigation

Upgrade Wireshark to version 0.99.6 or later to patch the infinite loop vulnerability in the SSL and MMS dissectors.

Fix this in Wireshark Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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