WiresharkApplication
CVE-2008-3139
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 · uneditedThe RTMPT dissector in Wireshark (formerly Ethereal) 0.99.8 through 1.0.0 allows remote attackers to cause a denial of service (crash) via unknown vectors. NOTE: this might be due to a use-after-free error.
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 · moderate confidenceA use-after-free vulnerability in the RTMPT dissector of Wireshark versions 0.99.8 through 1.0.0 allows remote attackers to cause a denial of service (crash) via malformed RTMPT packets in a capture file or network stream.
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
= 0.9.5= 0.99.2= 0.99.3= 0.99.4= 0.99.5= 0.99.6= 0.99.7= 0.99.8= 1.0= 1.0.0= 1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Wireshark is installedRun 'wireshark --version' or 'tshark --version' to see if Wireshark command-line tools are available on the systemAffected if The command returns a version number indicating Wireshark is installed
-
Determine the installed Wireshark versionExamine the version output from the previous step; look for version numbers in the 0.99.x or 1.0.x seriesAffected if The version matches 0.99.8, 0.99.9, 0.99.10, 1.0, or 1.0.0 specifically, or falls within the range 0.99.8 through 1.0.0
-
Verify RTMPT protocol support is presentCheck Wireshark dissector status by examining 'Edit > Preferences > Protocols > RTMPT' or run 'tshark -G dissectors' and look for RTMPT entryAffected if RTMPT dissector is available and enabled in the Wireshark installation
-
Confirm the system can process capture filesLook for capture file handling capability by checking if Wireshark can open pcap or pcapng files, or if the user has permissions to analyze network trafficAffected if The environment allows opening or processing packet capture files from external sources
A user is affected if Wireshark version 0.99.8 through 1.0.0 is installed and the RTMPT dissector is enabled, allowing malformed RTMPT packets in capture files to trigger the use-after-free crash.
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.
From vendor dataUpgrade Wireshark to a version after 1.0.0 that addresses this vulnerability. Avoid opening untrusted packet capture files from unknown sources.
Fix this in Wireshark
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-3139 — 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-2008-3139 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