dbcve.org
EtherealApplication · Ethereal Group

CVE-2005-1467

MEDIUM · 5.0 CVSS v2.0 Published 2005-05-05
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
Unknown vulnerability in the NDPS dissector in Ethereal before 0.10.11 allows remote attackers to cause a denial of service (memory exhaustion) via unknown 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 · high confidence

Memory exhaustion vulnerability in Ethereal's NDPS (Novell Distributed Print Services) dissector before version 0.10.11 allows remote attackers to cause denial of service by sending specially crafted network packets that trigger excessive memory allocation during packet dissection.

MitigationUpgrade to Ethereal 0.10.11 or later (or migrate to modern Wireshark). If legacy Ethereal must be used, disable the NDPS dissector or filter NDPS traffic at network perimeter.

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
EtherealApplication
Affected:= 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.5

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. Identify Ethereal installation and version
    Run 'ethereal -v' or check the application version through the UI (Help > About Ethereal)
    Affected if The installed version matches 0.8.x or 0.9.x series listed in affected versions (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.5)
  2. Verify NDPS dissector is loaded
    Open Ethereal and go to Analyze > Enabled Protocols. Search for 'NDPS' or 'NDS' in the protocol list and confirm it is enabled (checkbox checked)
    Affected if The NDPS protocol dissector is enabled in the protocol settings
  3. Check for NDPS traffic capture
    Start a capture or open an existing capture file. Use the filter 'ndps' or 'nds' in the display filter bar to see if any NDPS packets are present
    Affected if NDPS traffic is being dissected (visible in capture results)

You are affected if you have a vulnerable Ethereal version (0.8.x or 0.9.x) AND the NDPS dissector is enabled while processing network traffic that may contain NDPS packets.

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

Upgrade to Ethereal 0.10.11 or later (or migrate to modern Wireshark). If legacy Ethereal must be used, disable the NDPS dissector or filter NDPS traffic at network perimeter.

Fix this in Ethereal Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.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-2005-1467 — 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-2005-1467 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