[FD] ISPconfig v3.0.5.4 p6 - UI Exception & XSS Vulnerability

Document Title: =============== ISPconfig v3.0.5.4 p6 - UI Exception & XSS Vulnerability References (Source): ==================== http://ift.tt/2bmuJlD Release Date: ============= 2016-08-16 Vulnerability Laboratory ID (VL-ID): ==================================== 1909 Common Vulnerability Scoring System: ==================================== 3.5 Product & Service Introduction: =============================== ISPConfig 3 is an open-source server administration software for Linux and allows the management of one or more servers through a web-based front end. ISPConfig runs under the bsd open source license. (Copy of the Vendor Homepage: http://ift.tt/2bwzQnB ) Abstract Advisory Information: ============================== The vulnerability laboratory core research team discovered a stored cross site scripting vulnerability in the ISPconfig v3.0.5.4 p6. Vulnerability Disclosure Timeline: ================================== 2016-08-16: Public Disclosure (Vulnerability Laboratory) Discovery Status: ================= Published Affected Product(s): ==================== ISPConfig UG Product: ISPconfig - Hosting Service Panel (Web-Application) 3.0.5.4 p6 Exploitation Technique: ======================= Remote Severity Level: =============== Medium Technical Details & Description: ================================ A cross site scripting vulnerability has been uncovered in the official ISPconfig v3.0.5.4 p6 hosting panel web-application. The vulnerability allows remote attackers to inject own malicious script codes to the application-side of the vulnerable module. The cross site vulnerability is located in the `database username` input field of the database user module. The form of the add POST method request is not secure parsed by the basic validation. Thus allows to trigger a xss issue in the the edit form of the special crafted database username. The second execution point is located the exception-handling of the invalid input context. The exception-handling replies with the input of the invalid database username after an add was processed. The request method to inject is POST and the attack vector of the issue remains to the application-side of the service. The error exception issue is located to the client-side of the service and does not occur permanently. Due to the non protected session credentials an attacker is easily able to perform a malicious request by usage of a prepared web-link or web-page. The security risk of the xss vulnerability is estimated as medium with a cvss (common vulnerability scoring system) count of 3.3. Exploitation of the client-side vulnerability requires no privileged web-application user account and only low user interaction. Successful exploitation of the vulnerability results in non-persistent phishing attacks, session hijacking, non-persistent external redirect to malicious sources and non-persistent manipulation of affected or connected web module context. Request Method(s): [+] POST Vulnerable Module(s): [+] ./sites/ Vulnerable File(s): [+] database_user_edit.php Vulnerable Parameter(s): [+] Edit Formular [+] Invalid Exception-Handling Proof of Concept (PoC): ======================= The vulnerability can be exploited by remote attackers without privileged user account and with low user interaction. For security demonstration or to reproduce the vulnerability follow the provided information and steps below to continue. PoC: Exploitation via Database_User

PoC: (Execution) Database Users (Database Username Exception-Handling)

• Database username - c1>"%>" Invalid database user name. The username may contain these characters: a-z, A-Z, 0-9 and the underscore. Length: 2 - 64 characters.
  
• ... followwed by an execute in the edit form next to the vulnerable username input.

Database user

c1

%>"

Source: Gmail -> IFTTT-> Blogger