Menu

Star on GitHub · 3.2k

CVE-2006-1932

10.0 · HIGH

Off-by-one error in the OID printing routine in Ethereal 0.10.x up to 0.10.14 has unknown impact and remote attack vectors.

Published Apr 25, 2006ethereal_groupEPSS 2.64%

Overview

CVE-2006-1932 is a high-severity vulnerability affecting ethereal_group ethereal. It was published on April 25, 2006 and has a CVSS 2.0 base score of 10.0 (HIGH).

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

Technical description

Off-by-one error in the OID printing routine in Ethereal 0.10.x up to 0.10.14 has unknown impact and remote attack vectors.

Remediation

Check the references section for vendor advisories and patches from ethereal_group. Update ethereal 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-1932?

CVE-2006-1932 is a high-severity vulnerability affecting ethereal_group ethereal. It was published on April 25, 2006 and has a CVSS 2.0 base score of 10.0 (HIGH).

How severe is CVE-2006-1932?

This vulnerability has a CVSS 2.0 base score of 10.0, 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-1932?

Check the references section for vendor advisories and patches from ethereal_group. Update ethereal 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-1932?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2006-1932 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