# Vendor: Plesk Small Business Manager 10.2 + Site Editor # URL http://www.parallels.com/products/small-business-panel/ # Date: 2010-09-17
# Author : Hoyt LLC – http://xss.cx
# Home : http://cloudscan.me # Bug : Cross Site Scripting + SQL Injection # Tested on : Plesk Small Business Manager 10.2.0 // Windows 2008 /64/R2 # Disclosure : Uncoordinated # CVE ID's : CVE-2011-4763 -> 4768 ##############################################################http://www.parallels.com/products/plesk/sitebuilder/
http://xss.cx/examples/plesk-reports/plesk-10.2.0-site-editor.html
Parallels Plesk SiteBuilder is an easy to use, scalable web application designed to create and manage websites. This next-generation software can be integrated into any business process. Parallels Plesk SiteBuilder is the ideal marketing tool for converting your site traffic into a new client base.
Parallels Plesk Panel Add-ons
Parallels Plesk Panel lets you elevate your service offerings to the next level and enhance the versatility of your control panel with powerful add-on features and add-on products. View the interface in your native language, offer your customers anti-virus and anti-spam software, and/or an entire vault of applications including osCommerce and Mambo CMS software. Add-ons can be purchased a la carte or in our "Parallels Plesk Panel Power Pack" and "Parallels Plesk Panel Plus" bundled deals for additional savings.
NOTE: The Parallels Plesk Panel Professional Website Editor is NOT the same product as Parallels Plesk Sitebuilder, which includes a 5-step wizard for creating websites. The Parallels Plesk Panel Professional Website Editor does NOT include this wizard. For more information on Parallels Sitebuilder, please visit the Sitebuilder section of our website.
1. SQL injection nextThere are 7 instances of this issue:
- /Wizard/Edit/Html [currentPageId parameter]
- /Wizard/Edit/Modules
/ImageGallery [filelist cookie] - /Wizard/Edit/Modules
/ImageGallery/Image/Edit [PLESKSESSID cookie] - /Wizard/Publish [Referer HTTP header]
- /sites/78/78806f0057
ebcbb04597bd12795bd6a6/_ _edit/css/styles.css [colorScheme parameter] - /sites/78/78806f0057
ebcbb04597bd12795bd6a6/_ _edit/images/logo.gif [template parameter] - /sites/78/78806f0057
ebcbb04597bd12795bd6a6/_ _edit/images/xsk_16.jpg [colorScheme parameter]
2. Cross-site scripting (reflected) previous next
There are 3 instances of this issue:
Issue background
Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
No comments:
Post a Comment