WiresharkApplication
CVE-2008-1562
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 LDAP dissector in Wireshark (formerly Ethereal) 0.99.2 through 0.99.8 allows remote attackers to cause a denial of service (application crash) via a malformed packet, a different vulnerability than CVE-2006-5740.
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 confidenceWireshark versions 0.99.2 through 0.99.8 contain a flaw in the LDAP protocol dissector where parsing a malformed LDAP packet triggers an application crash, resulting in denial of service. The vulnerability stems from insufficient bounds checking or error handling when processing specially crafted LDAP packet data.
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.2= 0.99.3= 0.99.4= 0.99.5= 0.99.6= 0.99.7= 0.99.8CVSS 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 installedRun 'wireshark --version' or check your package manager for wireshark installationAffected if Wireshark is not installed on the system
-
Determine the installed Wireshark versionRun 'wireshark -v' or 'wireshark --version' to display the version numberAffected if The version displayed is 0.99.2, 0.99.3, 0.99.4, 0.99.5, 0.99.6, 0.99.7, or 0.99.8
-
Confirm LDAP dissector is availableLaunch Wireshark, go to Help > About Wireshark > Plugins or run 'tshark -G dissectors' to list loaded dissectors and verify ldap.dll or ldap.so existsAffected if The LDAP dissector is loaded and available in the installation
-
Check if Wireshark can process network capturesOpen a capture file or start a live capture that may contain LDAP traffic, or inspect if the LDAP protocol handler is active in the protocol preferencesAffected if You actively process LDAP traffic through Wireshark's dissector
You are affected if Wireshark versions 0.99.2 through 0.99.8 are installed and the LDAP dissector is available for processing network traffic.
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 version 0.99.9 or later, which contains the fix for this LDAP dissector crash vulnerability. Alternatively, avoid opening untrusted capture files from unknown sources.
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-2008-1562 — 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- secunia.com
- lists.opensuse.org
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- support.avaya.com
- wiki.rpath.com
- www.gentoo.org
- www.mandriva.com
- www.redhat.com
- www.securityfocus.com
- www.securityfocus.com
- www.securitytracker.com
- www.vupen.com
- www.vupen.com
- www.wireshark.org
- exchange.xforce.ibmcloud.com
- issues.rpath.com
- oval.cisecurity.org
- oval.cisecurity.org
- www.redhat.com
- www.redhat.com
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2008-1562 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