Menu

Star on GitHub · 3.2k

CVE-2006-3630

7.5 · HIGH

Multiple off-by-one errors in Wireshark (aka Ethereal) 0.9.7 to 0.99.0 have unknown impact and remote attack vectors via the (1) NCP NMAS and (2) NDPS dissectors.

Published Jul 21, 2006wiresharkCWE-189EPSS 1.94%

Overview

CVE-2006-3630 is a high-severity vulnerability affecting wireshark wireshark. It was published on July 21, 2006 and has a CVSS 2.0 base score of 7.5 (HIGH).

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

Multiple off-by-one errors in Wireshark (aka Ethereal) 0.9.7 to 0.99.0 have unknown impact and remote attack vectors via the (1) NCP NMAS and (2) NDPS dissectors.

Remediation

Check the references section for vendor advisories and patches from wireshark. Update wireshark to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2006-3630?

CVE-2006-3630 is a high-severity vulnerability affecting wireshark wireshark. It was published on July 21, 2006 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2006-3630?

This vulnerability has a CVSS 2.0 base score of 7.5, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2006-3630?

Check the references section for vendor advisories and patches from wireshark. Update wireshark to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2006-3630?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2006-3630 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2006

View all