Mercury SiteScope multiple fields cross-site scripting
| mercurysitescope-multiple-xss (29295) |
Description:
Mercury SiteScope is vulnerable to cross-site scripting, caused by improper validation of user-supplied input. A remote attacker could exploit this vulnerability using the "create name" or "description" field to inject malicious script into a Web page which would be executed in a victim's Web browser within the security context of the hosting Web site, once the page is viewed. An attacker could use this vulnerability to steal the victim's cookie-based authentication credentials.
Platforms Affected:
- Mercury, Mercury SiteScope 8.2
- Microsoft, Windows 2003 Server
Remedy:
No remedy available as of June 27, 2009.
Consequences:
Gain Access
References:
- BugTraq Mailing List, Fri Sep 29 2006 - 14:41:34 CDT , Mercury SiteScope 8.2 (8.1.2.0) Cross Site Scripting (XSS) Vulnerability at http://archives.neohapsis.com/archives/bugtraq/2006-09/0507.html.
- Mercury Web site, Mercury SiteScope at http://www.mercury.com/us/products/business-availability-center/sitescope/.
- BID-20275: Mercury SiteScope Unspecified HTML Injection Vulnerability
- CVE-2006-5122: Multiple cross-site scripting (XSS) vulnerabilities in Mercury SiteScope 8.2 (8.1.2.0) allow remote authenticated users to inject arbitrary web script or HTML via (1) any field create name field except create new group name or (2) any description field.
- SA22215: Mercury SiteScope Multiple Script Insertion Vulnerabilities
- VUPEN/ADV-2006-3888: Mercury SiteScope Multiple Variable Handling Cross Site Scripting Vulnerabilities
Reported:
Sep 29, 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
