WiresharkApplication
CVE-2006-5468
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 · uneditedUnspecified vulnerability in the HTTP dissector in Wireshark (formerly Ethereal) 0.99.3 allows remote attackers to cause a denial of service (crash) via unspecified vectors.
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 vulnerability in the HTTP dissector of Wireshark 0.99.3 allows remote attackers to cause a denial of service via crash. The vulnerability is in the protocol dissection functionality which processes HTTP traffic, and the specific vectors are not detailed in available documentation.
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.99.3CVSS 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.
-
Verify Wireshark is installedCheck for Wireshark installation by running 'which wireshark' on Linux/Mac or checking Program Files on Windows. Also try 'wireshark --version' to get version info.Affected if Wireshark is installed on the system
-
Identify the installed Wireshark versionRun 'wireshark --version' or 'wireshark -v' from command line. On Windows, right-click Wireshark.exe and select Properties > Details to see the File Version.Affected if The installed version is exactly 0.99.3
-
Confirm HTTP dissector is enabledOpen Wireshark, go to Analyze > Enabled Protocols. Scroll to find HTTP in the list and verify the checkbox is checked (enabled by default).Affected if HTTP protocol dissector is enabled (this is the default state)
-
Check for recent crash logsLook for crash dump files or logs in the Wireshark program directory, user home directory, or system temp folders. On Linux check /var/crash or ~/.wireshark. On Windows check Event Viewer for Application errors.Affected if Wireshark has crashed recently while processing network traffic
You are affected if Wireshark version 0.99.3 is installed and the HTTP dissector is enabled, which it is by default.
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 the latest version which contains the fixed HTTP dissector code. If upgrade is not immediately feasible, consider disabling the HTTP dissector or using packet capture filters to limit exposure to untrusted network traffic.
Fix this in Wireshark
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-5468 — 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 sources- patches.sgi.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- securitytracker.com
- support.avaya.com
- www.kb.cert.org
- www.mandriva.com
- www.novell.com
- www.redhat.com
- www.securityfocus.com
- www.securityfocus.com
- www.vupen.com
- www.wireshark.org
- exchange.xforce.ibmcloud.com
- issues.rpath.com
- oval.cisecurity.org
- oval.cisecurity.org
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2006-5468 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