Wireshark up to 0.99.3 memory allocation

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.8$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in Wireshark up to 0.99.3. Affected by this vulnerability is an unknown functionality. The manipulation leads to memory allocation. This vulnerability is documented as CVE-2006-4805. There is not any exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Wireshark up to 0.99.3 (Packet Analyzer Software). It has been rated as problematic. This issue affects some unknown processing. The manipulation with an unknown input leads to a memory allocation vulnerability. Using CWE to declare the problem leads to CWE-789. The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated. Impacted is availability. The summary by CVE is:

epan/dissectors/packet-xot.c in the XOT dissector (dissect_xot_pdu) in Wireshark (formerly Ethereal) 0.9.8 through 0.99.3 allows remote attackers to cause a denial of service (memory consumption and crash) via an encoded XOT packet that produces a zero length value when it is decoded.

The bug was discovered 10/27/2006. The weakness was released 10/27/2006 as confirmed advisory (CERT.org). It is possible to read the advisory at kb.cert.org. The identification of this vulnerability is CVE-2006-4805 since 09/15/2006. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available.

It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 36335 (CentOS 3 / 4 : wireshark (CESA-2006:0726)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CentOS Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 156229 (Oracle Enterprise Linux Update for Wireshark (ELSA-2006:0726,ELSA-2006:0658,ELSA-2006:0602)).

Upgrading eliminates this vulnerability. A possible mitigation has been published 2 weeks after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (29843), Tenable (36335), SecurityFocus (BID 20762†), OSVDB (30070†) and Secunia (SA22590†). Entries connected to this vulnerability are available at VDB-31382, VDB-31381, VDB-31380 and VDB-31379. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 4.8

VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Memory allocation
CWE: CWE-789 / CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 36335
Nessus Name: CentOS 3 / 4 : wireshark (CESA-2006:0726)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 57563
OpenVAS Name: Debian Security Advisory DSA 1201-1 (ethereal)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Timelineinfo

09/15/2006 🔍
10/27/2006 +42 days 🔍
10/27/2006 +0 days 🔍
10/27/2006 +0 days 🔍
10/27/2006 +0 days 🔍
10/27/2006 +0 days 🔍
10/27/2006 +0 days 🔍
11/05/2006 +9 days 🔍
11/09/2006 +4 days 🔍
04/23/2009 +896 days 🔍
03/12/2015 +2149 days 🔍
04/25/2026 +4062 days 🔍

Sourcesinfo

Product: wireshark.org

Advisory: kb.cert.org
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2006-4805 (🔍)
GCVE (CVE): GCVE-0-2006-4805
GCVE (VulDB): GCVE-100-33011

OVAL: 🔍

CERT: 🔍
X-Force: 29843
SecurityFocus: 20762 - Wireshark Multiple Protocol Dissectors Denial of Service Vulnerabilities
Secunia: 22590
OSVDB: 30070 - CVE-2006-4805 - Wireshark - Denial of Service Issue
SecurityTracker: 1017129
Vulnerability Center: 13045 - Wireshark Remote Denial of Service Via an Encoded XOT Packet, Medium
Vupen: ADV-2006-4220

See also: 🔍

Entryinfo

Created: 03/12/2015 22:21
Updated: 04/25/2026 20:15
Changes: 03/12/2015 22:21 (73), 07/10/2019 14:44 (13), 01/14/2025 07:08 (17), 04/25/2026 20:15 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!