Vulnerability Assessment & Network Security Forums
If through a vulnerability assessment, a network security issue is detected for the vulnerability below, applying the appropriate security patches in a timely matter is very important. If you have detected that your system has already been compromised, following CERT's Network Security recovery document will assist with recommended steps for system recovery.
Vulnerability Assessment Details
Ethereal: Multiple vulnerabilities
Detailed Explanation for this Vulnerability Assessment
The remote host is affected by the vulnerability described in GLSA-200412-15
(Ethereal: Multiple vulnerabilities)
There are multiple vulnerabilities in versions of Ethereal earlier
than 0.10.8, including:
Bug in DICOM dissection
discovered by Bing could make Ethereal crash (CAN 2004-1139).
An invalid RTP timestamp could make Ethereal hang and create a
large temporary file (CAN 2004-1140).
The HTTP dissector could
access previously-freed memory (CAN 2004-1141).
discovered that an improperly formatted SMB could make Ethereal hang
A possible hacker might be able to use these vulnerabilities to crash
Ethereal, perform DoS by CPU and disk space utilization or even execute
arbitrary code with the permissions of the user running Ethereal, which
could be the root user.
For a temporary workaround you can disable all affected protocol
dissectors by selecting Analyze->Enabled Protocols... and deselecting
them from the list. However, it is strongly recommended to upgrade to
the latest stable version.
All ethereal users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=net-analyzer/ethereal-0.10.8"
Network Security Threat Level: High
Networks Security ID:
Vulnerability Assessment Copyright: (C) 2005 Michel Arboi
|Ericsson Redback EIM10GE-SE12-4 4Pt 10G ROA128 3242/1
|Radware LinkProof APSolute Application Delivery
|Radware LinkProof APSolute Application Delivery 1000/ASII/5xGb+16xFE/256MB
|Huawei GPFD with B+ C+ C++ transceivers. See Descriptions for details
No Discussions have been posted on this vulnerability.