CipherTrust IronMail URL directory traversal
| ironwebmail-url-directory-traversal (29620) |
Description:
CipherTrust IronMail is vulnerable to a directory traversal, caused by improper validation in the IronWebMail module when processing HTTP requests. A remote attacker could send a specially-crafted HTTP GET request containing URL encoded "dot dot" sequences (%252e..%252e) for an IM_FILE identifier to traverse directories and view arbitrary files on the system.
Platforms Affected:
- CipherTrust, IronMail 6.1.1
Remedy:
Apply Ironmail 6.1.1 Hotfix 17, available from the CipherTrust IronMail Web site. See References.
Consequences:
Obtain Information
References:
- CipherTrust IronMail Web site, Secure Email Gateway Appliance & Enterprise Email Anti-Virus Security Solutions at https://supportcenter.ciphertrust.com/index.php?url=https://supportcenter.ciphertrust.com/vulnerability/IWM501-01.php.
- SYMSA-2006-010, Directory Traversal in IronWebMail at http://www.symantec.com/enterprise/research/SYMSA-2006-010.txt.
- BID-20436: IronWebMail Directory Traversal Information Disclosure Vulnerability
- CVE-2006-5210: Directory traversal vulnerability in IronWebMail before 6.1.1 HotFix-17 allows remote attackers to read arbitrary files via a GET request to the IM_FILE identifier with double-url-encoded ../ sequences (%252e%252e/).
- SA22406: IronMail IronWebMail Directory Traversal Vulnerability
- SECTRACK ID: 1017069: IronWebMail IM_FILE Request Lets Remote Users Traverse the Directory
- VUPEN/ADV-2006-4055: CipherTrust IronMail IronWebMail HTTP Request Directory Traversal Vulnerability
Reported:
Oct 16, 2006
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
