CVE-2005-1456
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 · uneditedMultiple unknown vulnerabilities in the (1) DHCP and (2) Telnet dissectors in Ethereal before 0.10.11 allow remote attackers to cause a denial of service (abort).
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 confidenceThis CVE affects Ethereal (now Wireshark) versions prior to 0.10.11. The DHCP and Telnet protocol dissectors contain vulnerabilities that can be exploited by specially crafted network packets to cause the application to abort, resulting in a denial of service. Attackers can trigger this by sending malicious DHCP or Telnet traffic to a system running Ethereal with packet capture privileges.
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= 0.8= 0.8.13= 0.8.14= 0.8.15= 0.8.18= 0.8.19= 0.9= 0.9.1= 0.9.2= 0.9.3= 0.9.4= 0.9.5CVSS 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.
-
Identify installed Ethereal or Wireshark versionRun 'ethereal -v' or 'wireshark -v' from command line, or check the application via package manager (dpkg -l | grep -i ethereal or rpm -qa | grep -i ethereal)Affected if The version displayed is 0.10.10 or earlier, or matches any of these affected versions: 0.8.x, 0.9.x through 0.9.5
-
Confirm packet capture functionality is activeVerify that the user running Ethereal has packet capture privileges. On Linux, check group membership (typically 'pcap' group) using 'groups' command, or verify libpcap is installed and accessibleAffected if The user has raw packet capture privileges and can capture network traffic with Ethereal
-
Verify DHCP or Telnet dissectors are enabledIn the Ethereal GUI, go to Analyze > Enabled Protocols and check if 'DHCP' or 'Telnet' protocols are enabled, or inspect configuration files for dissector settingsAffected if DHCP or Telnet protocol dissectors are enabled in the capture configuration
A user is affected if running Ethereal version 0.10.10 or earlier with packet capture privileges and DHCP or Telnet dissectors enabled, making the system vulnerable to denial of service from malicious network packets.
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 Ethereal to version 0.10.11 or later (or migrate to current Wireshark releases). If immediate patching is not feasible, restrict packet capture privileges and monitor for suspicious DHCP/Telnet traffic to minimize exposure.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-1456 — 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-2005-1456 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