Document Title: =============== Magento MarketPlace T1 - Bypass & Persistent Vulnerability References (Source): ==================== http://www.vulnerability-lab.com/get_content.php?id=1902 Release Date: ============= 2018-06-18 Vulnerability Laboratory ID (VL-ID): ==================================== 1902 Common Vulnerability Scoring System: ==================================== 4.2 Vulnerability Class: ==================== Cross Site Scripting - Persistent Current Estimated Price: ======================== 500€ - 1.000€ Product & Service Introduction: =============================== Magento is an open-source e-commerce platform written in PHP. The software was originally developed by Varien Inc., a US private company headquartered in Culver City, California, with assistance from volunteers. Varien published the first general-availability release of the software on March 31, 2008. Roy Rubin, former CEO of Varien, later sold a substantial share of the company to eBay, which eventually completely acquired and then spun off the company. (Copy of the Homepage: https://en.wikipedia.org/wiki/Magento ) Abstract Advisory Information: ============================== The vulnerability laboratory core research team discovered a filter bypass and input validation vulnerability in the official Magento MarketPlace web-application. Vulnerability Disclosure Timeline: ================================== 2018-06-18: Public Disclosure (Vulnerability Laboratory) Discovery Status: ================= Published Affected Product(s): ==================== Magento Product: MarketPlace - Online Service (Web-Application) 2016 Q3 Exploitation Technique: ======================= Remote Severity Level: =============== Medium Authentication Type: ==================== No authentication (guest) User Interaction: ================= Low User Interaction Disclosure Type: ================ Bug Bounty Program Technical Details & Description: ================================ An application-side input validation and mail encode vulnerability has been discovered in the magento marketplace online service web-application. The persistent vulnerability allows remote attackers to inject own malicious script codes to the application-side of the affected module. The vulnerability is located in the firstname parameter of the magento marketplace outgoing service mail context. Remote attackers are able to inject a malicious payload as firstname to the web-application. Thus can be handled during the sync registration of the portal because of the same origin policy. After the registration the attacker can change the email to spoof the input context of the firstname that is read by the outgoing generated mail service in html. The firstname input is influenced by the attacker to manipulate the email body context of the original info@magento.com email address. The site validation itself disallows to register with thus type of payload in the firstname. The attacker can bypass this by a manipulated main account that is used to sync with the marketplace notification of moderator/administrator interaction. The method takes a bit time, but is more successful on exploitation because of the target can not be identified as the evil sender (attacker). Reason is that he sends the email through the mail info@magento.com service of the web-application as original email address. Remember that the email which is saved via profile is used for the mailings. Thus results as well in the problemtic that leads to email message body context spoofing. The issues does only affect the new magento marketplace web-application. Different issues reported with the same type was already fixed as valid bug bounty in the imagine, main site, shop and enterprise web-applications of magento. The attack vector of the vulnerability is located on the application-side of the online service and the request method to inject is POST. The security risk of the application-side vulnerability is estimated as medium with a cvss (common vulnerability scoring system) count of 3.5. Exploitation of the persistent vulnerability requires a low privileged magento user account with restricted access and with low user interaction. Successful exploitation of the vulnerabilities results in persistent phishing mails, session hijacking, persistent external redirect to malicious sources and application-side manipulation of affected or connected module context. Request Method(s): (Inject) [+] POST Vulnerable Module(s): [+] MarketPlace Magento Affcted Module(s): [+] Mail Notify - (New Top Extensions on Magento Marketplace) Internal Sender(s): [+] info@magento.com External Email(s): (Account) [+] tester23@evolution-sec.com Proof of Concept (PoC): ======================= The persistent vulnerability can be exploited by remote attackers with low privilege magento 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. Register a magento account with test payload in the firstname 2. Subscribe to the events that delivers new events via email notify 3. Check the email inbox 4. The payload executes in the email body next to the Dear name introduction 5. Successful reproduce of the application-side vulnerability! Note: Random mails can be compromised by sending malicious code of the original magento marketplace post inbox. --- Mail Header Information Log --- Betreff: New Top Extensions on Magento Marketplace Von: Magento Datum: 08.08.2016 17:28 An: tester23@evolution-sec.com PoC: Exploitation (Mail Body: New Top Extensions on Magento Marketplace)  

New Top Extensions on Marketplace

 

Dear ">[PERSISTENT SCRIPT CODE EXECUTION!]