EMC Retrospect password hash information disclosure
| retrospect-passwordhash-info-disclosure (43930) |  Low Risk |
Description:
EMC Retrospect could allow a remote attacker to obtain sensitive information, caused by the transmitting of the client password hash in plain text. By sending specially-crafted packets to the Backup Client, a remote attacker could exploit this vulnerability to obtain the password hash and possibly other sensitive information, which could be used to launch further attacks against the affected system.
Platforms Affected:
- EMC, Retrospect Client 7.5.116
Remedy:
Upgrade to the latest version of EMC Retrospect (7.6 or later), available from the EMC Web site. See References.
Consequences:
Obtain Information
References:
- BugTraq Mailing List, Mon Jul 21 2008 - 08:45:55 CDT , EMC Dantz Retrospect 7 backup Client PlainText Password Hash Disclosure Vulnerability at http://archives.neohapsis.com/archives/bugtraq/2008-07/0171.html.
- EMC Web site, Product Downloads & Updates at http://www.emcinsignia.com/supportupdates/updates/.
- FortiGuard Advisory (FGA-2008-16), Multiple vulnerabilities in EMC Dantz Retrospect Backup Client/Server at http://www.fortiguardcenter.com/advisory/FGA-2008-16.html.
- BID-30308: EMC Retrospect Backup Client Password Hash Information Disclosure Vulnerability
- CVE-2008-3289: EMC Dantz Retrospect Backup Client 7.5.116 sends the password hash in cleartext at an unspecified point, which allows remote attackers to obtain sensitive information via a crafted packet.
- SA31186: EMC Retrospect Multiple Vulnerabilities
- VUPEN/ADV-2008-2150: EMC Retrospect Denial of Service and Information Disclosure Issues
Reported:
Jul 18, 2008
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net