dbcve.org
WiresharkApplication

CVE-2008-1070

MEDIUM · 5.0 CVSS v2.0 Published 2008-02-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The SCTP dissector in Wireshark (formerly Ethereal) 0.99.5 through 0.99.7 allows remote attackers to cause a denial of service (crash) via a malformed packet.

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

The SCTP dissector in Wireshark 0.99.5 through 0.99.7 crashes when processing a malformed SCTP packet, causing a denial of service. The vulnerability is triggered when Wireshark parses a specifically crafted packet during packet capture analysis.

MitigationUpdate Wireshark to version 0.99.8 or later, which contains the fix for this vulnerability. Avoid opening packet captures from untrusted 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:= 0.6= 0.7.9= 0.8.16= 0.9.10= 0.10= 0.10.4= 0.10.13= 0.99= 0.99.1= 0.99.2= 0.99.3= 0.99.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
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. Confirm Wireshark is installed
    Run `wireshark --version` or `tshark --version` to display the installed Wireshark version
    Affected if The command returns a version number
  2. Compare installed version to vulnerable range
    Check if the displayed version falls between 0.99.5 and 0.99.7 inclusive
    Affected if Version is 0.99.5, 0.99.6, or 0.99.7
  3. Identify if SCTP protocol is being dissected
    Open a packet capture file or capture live traffic, then in Wireshark look for SCTP packets in the packet list or use display filter 'sctp'
    Affected if SCTP packets are present and being parsed by the dissector

You are affected if Wireshark version 0.99.5, 0.99.6, or 0.99.7 is installed AND SCTP traffic is being analyzed, as the malformed packet will cause a crash in the SCTP dissector.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Wireshark to version 0.99.8 or later, which contains the fix for this vulnerability. Avoid opening packet captures from untrusted sources.

Fix this in Wireshark Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing0.5 h
  • Review / QA0.5 h
3.0 hours of engineering $750
Get help mitigating

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-2008-1070 — 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-2008-1070 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