dbcve.org
WiresharkApplication

CVE-2007-3393

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
Off-by-one error in the DHCP/BOOTP dissector in Wireshark before 0.99.6 allows remote attackers to cause a denial of service (crash) via crafted DHCP-over-DOCSIS packets.

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

An off-by-one error exists in the DHCP/BOOTP packet dissector in Wireshark versions prior to 0.99.6. When the dissector processes specially crafted DHCP-over-DOCSIS packets, the boundary error causes a buffer overflow or underflow that leads to a crash (denial of service).

MitigationUpgrade Wireshark to version 0.99.6 or later. Alternatively, avoid processing untrusted DHCP-over-DOCSIS capture files until the upgrade is applied.

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 Wireshark version
    Run 'wireshark --version' or 'tshark -v' to identify the installed Wireshark version
    Affected if The version displayed is 0.99.5 or earlier (any version <= 0.99.5)
  2. Confirm DHCP/BOOTP dissector is active
    Open Wireshark, go to Analyze > Enabled Protocols, and verify if DHCP or BOOTP protocol is enabled
    Affected if DHCP or BOOTP dissector is enabled and the version is <= 0.99.5
  3. Check for DHCP-over-DOCSIS traffic
    Inspect any capture files (pcap) for DHCP-over-DOCSIS packets using 'tshark -r capture.pcap -Y docsis.dhcp' or examine the protocol hierarchy in Wireshark
    Affected if DHCP-over-DOCSIS packets are being dissected and the Wireshark version is <= 0.99.5

You are affected if Wireshark version 0.99.5 or earlier is installed AND the DHCP/BOOTP dissector is enabled while processing DHCP-over-DOCSIS traffic or capture 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. Alternatively, avoid processing untrusted DHCP-over-DOCSIS capture files until the upgrade is applied.

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-2007-3393 — 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-3393 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