[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Getdpd Bug Bounty #6 - (Import - FTP) Persistent Vulnerability
Getdpd Bug Bounty #6 - (Import) Persistent Vulnerability
Vulnerability Laboratory ID (VL-ID):
Common Vulnerability Scoring System:
Product & Service Introduction:
DPD is an all-in-one shopping cart and digital fulfillment service for downloadable products. Serving thousands of stores, DPD processes and
delivers millions worth of downloads each year.
(Copy of the Vendor Homepage: https://getdpd.com/security )
Abstract Advisory Information:
The Vulnerability Laboratory Research team discovered an application-side input validation web vulnerability in the official Getpdp online service web-application.
Vulnerability Disclosure Timeline:
2015-08-09: Researcher Notification & Coordination (Hadji Samir - Evolution Security GmbH)
2015-08-10: Vendor Notification (Getdpd Security Team - Bug Bounty Program)
2015-09-02: Vendor Response/Feedback (Getdpd Security Team - Bug Bounty Program)
2015-02-01: Vendor Fix/Patch (Getdpd Developer Team)
2015-02-09: Public Disclosure (Vulnerability Laboratory)
DPD - Digital Product Delivery
Product: DPD Online Service (Web-Application) 2016 Q1
Technical Details & Description:
An application-side cross site scripting web vulnerability has been discovered in the official Getdpd online service web-application.
The security vulnerability allows remote attackers to inject own script code to the application-side of the affected application module.
The vulnerability is located in the filename value of the attachment file upload with FTP. Remote attackers with low privilege web-application
user accounts are able to inject own malicious script code via upload file with FTP method request to the application-side. The injection point
is the vulnerable filename parameter in the upload file with FTP and with POST method request and the execution point is located in attachment
file Import Product from FTP Drop Box. The request method to https://getdpd.com/storefront/bulkimport inject is Upload file with FTP and the
vulnerability is located to the application-side of the vulnerable online-service. The execution context is executed by the vulnerable
notification error value.
The security risk of the application-side file validation vulnerability is estimated as medium with a cvss (common vulnerability scoring system) count of 4.4.
Exploitation of the persistent input validation web vulnerability requires a low privilege 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.
[+] Import Prodcut from FTP (exp. Dropbox)
[+] Product Name (Input Field)
[+] notification error
Proof of Concept (PoC):
The security vulnerability can be exploited by remote attackers with low privilege web-application 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- Connect to ftp.getdpd.com with username and password
2- Upload file with Payload name (code injection)
3- Go to https://getdpd.com/storefront/bulkimport
4- Select the file and click to Import Selected File
5- The malicious code will execute
--- PoC Session Logs [POST] ---
Load Flags[LOAD_DOCUMENT_URI LOAD_INITIAL_DOCUMENT_URI ] Content Size Mime Type[text/html]
User-Agent[Mozilla/5.0 (X11; Linux i686; rv:39.0) Gecko/20100101 Firefox/39.0]
Date[Mon, 10 Aug 2015 15:58:07 GMT]
Expires[Thu, 19 Nov 1981 08:52:00 GMT]
Cache-Control[no-store, no-cache, must-revalidate, post-check=0, pre-check=0]
P3p[CP="NOI CURa OUR NOR UNI"]
Set-Cookie[_csrf_token=5dd0e8de2f12cbf4cfdddb7af46239126a7861de; path=/; secure]
PoC: Source - BulkImport (FTP Import _ DPD Shopping Cart.html)
<div class="notification error">
<span class="strong">Please correct the following:</span>
"><iframe src="FTP%20Import%20%7C%20DPD%20Shopping%20Cart_files/x.html" onload="alert(document.cookie)">
.png: No price.
<style type="text/css" media="screen">
<h2>Bulk FTP Import</h2>
<div class="well well-small">
<p>Enter the following information into your FTP client.
We recommend using <a href="http://filezilla-project.org/"
target="_blank">FileZilla</a> (Windows) or <a
href="http://cyberduck.ch/" target="_blank">Cyberduck</a> (OS
X) if you do not already have a FTP program.</p>
<p><em><strong>Please note:</strong> The
FTP drop box is write-only and uploaded files will be automatically
removed after one week.</em></p>
<legend>FTP Connection Information</legend>
<label for="name" class="control-label">Host /
Solution - Fix & Patch:
The vulnerability can be patched by a secure parse and encode of the vulnerable product name value in the upload POST method request. Restrict the input and disallow usage of special chars.
Filter and setup a secure exception handling that prevents the persistent execution in the output location were the ftp file bulkimport list becomes visible.
Disallow usage of multiple productnames as extension to prevent arbitrary file upload of webshells. Secure the type of file to secure the mechanism by manual interaction.
The security risk of application-side input validation web vulnerability in the frontend of the getdpd web-application is estimated as medium. (CVSS 4.4)
Credits & Authors:
Vulnerability Laboratory [Research Team] - Hadji Samir [samir@xxxxxxxxxxxxxxxxx] [www.vulnerability-lab.com] (http://www.vulnerability-lab.com/show.php?user=Hadji%20Samir)
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@xxxxxxxxxxxxxxxxxxxxx - research@xxxxxxxxxxxxxxxxxxxxx - admin@xxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxx or research@xxxxxxxxxxxxxxxxxxxxx) to get a permission.
Copyright © 2016 | Vulnerability Laboratory - [Evolution Security GmbH]™
VULNERABILITY LABORATORY - RESEARCH TEAM