[FD] VoipNow v4.0.1 - (xajax_handler) Persistent Vulnerability

Document Title: =============== VoipNow v4.0.1 - (xajax_handler) Persistent Vulnerability References (Source): ==================== http://ift.tt/1T8mAPl Release Date: ============= 2016-04-26 Vulnerability Laboratory ID (VL-ID): ==================================== 1828 Common Vulnerability Scoring System: ==================================== 3.8 Product & Service Introduction: =============================== A cloud communications platform dedicated to service providers and organizations in need of robust enterprise PBX, video, presence, instant messaging, contact center features, conferencing, faxing, and mobility. Used by more than 10,000 service providers worldwide. (Copy of the Homepage: http://ift.tt/1pBgBup ) Abstract Advisory Information: ============================== The vulnerability laboratory core research team discovered an application-side input validation vulnerability in the VoipNow v4.0.1 web-application. Vulnerability Disclosure Timeline: ================================== 2016-03-18: Researcher Notification & Coordination (Benjamin Kunz Mejri - Evolution Security GmbH) 2016-03-19: Vendor Notification (VoipNow Support Team) 2016-04-25: Public Disclosure (Vulnerability Laboratory) Discovery Status: ================= Published Affected Product(s): ==================== 4PSA Product: VoipNow - Online Service (Web-Application) 4.0.1 Exploitation Technique: ======================= Remote Severity Level: =============== Medium Technical Details & Description: ================================ An application-side input validation web vulnerability has been discovered in the official VoipNow v4.0.1 web-application. The vulnerability allows remote attacker to inject own malicious script codes to the application-side of the vulnerable service. The persistent vulnerability is located in the `report_block_table_details` and `report_block_table_title` values of the `xajax_handler.php` file GET method request. Remote attackers are able to inject own malicious script codes to the Notes input field in the invoice template. Thus allows an attacker to trigger an execution of the payload on edit or active invoice interaction. The request method to inject is POST via input and the attack vector of the issue is located on the application-side of the service. The security risk of the application-side vulnerability is estimated as medium with a cvss (common vulnerability scoring system) count of 3.8. Exploitation of the persistent web vulnerability requires a low privilege web-application user account and low or medium user interaction. Successful exploitation of the vulnerability results in session hijacking, persistent phishing attacks, persistent external redirects to malicious source and persistent manipulation of affected or connected application modules. Request Method(s): [+] POST Vulnerable Module(s): [+] Invoice - Template Vulnerable File(s): [+] xajax_handler.php Vulnerable Inputs(s): [+] Add Note Vulnerable Parameter(s): [+] report_block_table_details [+] report_block_table_title Proof of Concept (PoC): ======================= The persistent input validation web vulnerability can be exploited by remote attackers with low privileged web-application user account and low user interaction. For security demonstration or to reproduce the vulnerability follow the provided information and steps below to continue. Manual steps to reproduce the vulnerability ... 1. Open the main website 2. Login to the application 3. Open Invoices Management - Invoice Number as Template 4. Inject to the Note description input field on buttom the malicious payload 5. Save the request via POST method 6. Watch the printed site or the edit invoice formular to trigger the persistent script code execution 7. Successful reproduce of the application-side vulnerability! PoC: (report_block_table_details)

By VoipNow at Apr 16, 2016 16:45:19

>"><[PERSISTENT INJECTED SCRIPT CODE!]>

Source: Gmail -> IFTTT-> Blogger