Latest YouTube Video

Friday, January 12, 2018

[FD] Magento Connect T1 - (Claim) Persistent Vulnerability

Document Title: =============== Magento Connect T1 - (Claim) Persistent Vulnerability References (Source): ==================== http://ift.tt/2msTmo7 Release Date: ============= 2018-01-08 Vulnerability Laboratory ID (VL-ID): ==================================== 1469 Common Vulnerability Scoring System: ==================================== 3.8 Vulnerability Class: ==================== Cross Site Scripting - Persistent Current Estimated Price: ======================== 1.000€ - 2.000€ Product & Service Introduction: =============================== Magento is an open source e-commerce web application that was launched on March 31, 2008 under the name Bento. It was developed by Varien (now Magento, a division of eBay) with help from the programmers within the open source community but is now owned solely by eBay Inc. Magento was built using parts of the Zend Framework. It uses the entity-attribute-value (EAV) database model to store data. In November 2013, W3Techs estimated that Magento was used by 0.9% of all websites. Our team of security professionals works hard to keep Magento customer information secure. What`s equally important to protecting this data? Our security researchers and user community. If you find a site that isn`t following our policies, or a vulnerability inside our system, please tell us right away. ( Copy of the Vendor Homepage: http://ift.tt/1E22539 & http://ift.tt/1E22539 ) Abstract Advisory Information: ============================== The Vulnerability Laboratory Research Team discovered an application-side cross site scripting web vulnerabilityin the Magento Connect web-application. Vulnerability Disclosure Timeline: ================================== 2018-01-08: Public Disclosure (Vulnerability Laboratory) Discovery Status: ================= Published Affected Product(s): ==================== Ebay Inc. Product: Magento - Connect Web Application 2015 Q2 Exploitation Technique: ======================= Remote Severity Level: =============== Medium Technical Details & Description: ================================ A persistent cross site scripting web vulnerability has been discovered in the official Magento Connect web-application. The vulnerability allows remote attackers to inject own script code on the application-side of the affected application module. The vulnerability is located in the `claim%5Bclaimed_extension_url` value of the `magento-connect/claim/claim/new/` module. Remote attackers are able to inject own script code on the application-side of the service to compromise user/moderator/admin session data. The request method to inject is POST and the attack vector is located on the application-side of the affected module. The security risk of the web vulnerability is estimated as medium with a cvss (common vulnerability scoring system) count of 3.8. Exploitation of the persistent input validation web vulnerability requires a low privileged 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 (api). Request Method(s): [+] POST Vulnerable Service(s): [+] Magento Connect Vulnerable Module(s): [+] magento-connect/claim/claim/new/ Vulnerable Parameter(s): [+] claim%5Bclaimed_extension_url Proof of Concept (PoC): ======================= The issue in the exception handling can be exploited by remote attackers with privileged application user account and low or medium user interaction. For security demonstration or to reproduce the security vulnerability follow the provided information and steps below to continue. Manual steps to reproduce the vulnerability ... 1. Surf to http://ift.tt/1GWr3iz 2. In the enter a link to the extension on Connect you have to inject the payload via http session tamper Note: Payload "> 3. Successful reproduce of the persistent xss security vulnerability! POC: Exception Handling
[MALICIOUS PAYLOAD EXECUTION POINT!]"> Required field. Example: http://ift.tt/2EnUG1R


Source: Gmail -> IFTTT-> Blogger

No comments: