Document Title:
===============
Phone Drive v3.0.3 iOS - Multiple Critical Vulnerabilities
References (Source):
====================
http://www.vulnerability-lab.com/get_content.php?id=1037
Release Date:
=============
2013-07-30
Vulnerability Laboratory ID (VL-ID):
====================================
1037
Common Vulnerability Scoring System:
====================================
7.6
Product & Service Introduction:
===============================
You can now use your iOS device as a portable Wireless Flash Drive. Introducing Phone Drive.
Phone Drive allows you to store, view and manage files on your iPhone or iPad. You can connect
to Phone Drive from any Mac or PC over the Wi-Fi network and transfer files by drag & drop files
straight from the Finder or Windows Explorer. Phone Drive features document viewer, PDF reader,
music player, image viewer, voice recorder, text editor, file manager and support most of the
file operations: like delete, move, copy, email, share, zip, unzip and more.
( Copy of the Homepage: https://itunes.apple.com/de/app/phone-drive/id431033044 )
Abstract Advisory Information:
==============================
The Vulnerability Laboratory Research Team discovered 2 persistent web vulnerabilities in the Phone Drive v3.0.3 application (Apple iOS - iPad & iPhone).
Vulnerability Disclosure Timeline:
==================================
2013-07-31: Public Disclosure (Vulnerability Laboratory)
Discovery Status:
=================
Published
Affected Product(s):
====================
Apple AppStore
Product: Phone Drive - Mobile Application 3.0.3
Exploitation Technique:
=======================
Remote
Severity Level:
===============
High
Technical Details & Description:
================================
1.1
A local command/path injection web vulnerability is detected in the Phone Drive v3.0.3 application (Apple iOS - iPad & iPhone).
The vulnerability allows to inject local commands via vulnerable system values to compromise the apple mobile iOS application.
The vulnerability is located in the index file dir (header) listing module when processing to request and list the ipad or
iphone devicename. Local attackers can change the name of the device to inject the code and request any local path or inject
commands on application-side. The malicious context with the path request executes when a user or victim is watching the
file dir index listing.
Exploitation of the web vulnerability requires a local privilege iOS device account with restricted access and no user interaction.
Successful exploitation of the vulnerability results unauthorized execution of system specific commands and path requests.
Vulnerable Application(s):
[+] Phone Drive v3.0.3 - ITunes or AppStore (Apple)
Vulnerable Parameter(s):
[+] device name
Affected Module(s):
[+] Listing (INDEX & SUB CATEGORIES) - Page Header
1.2
A local command/path injection web vulnerability is detected in the Phone Drive v3.0.3 application (Apple iOS - iPad & iPhone).
The vulnerability allows to inject local commands via vulnerable system values to compromise the apple mobile iOS application.
The vulnerability is located in the file dir foldername listing module when processing to request and list the foldernames as item.
Local attackers can change the name of the foldernames to inject the code and request any local path or inject commands on application-side.
The malicious context with the path request executes when a user or victim is watching the file dir foldername listing.
Exploitation of the web vulnerability requires a local privilege iOS device account with restricted access and no user interaction.
Successful exploitation of the vulnerability results unauthorized execution of system specific commands and path requests.
Vulnerable Application(s):
[+] Phone Drive v3.0.3 - ITunes or AppStore (Apple)
Vulnerable Parameter(s):
[+] foldername (add/create)
Affected Module(s):
[+] Folder Listing (INDEX & SUB CATEGORIES)
1.3
A persistent input validation web vulnerability is detected in the Phone Drive v3.0.3 application (Apple iOS - iPad & iPhone).
The bug allows an attacker (remote) to implement/inject malicious own malicious persistent script codes (application-side).
The vulnerability is located in the `rename file` module of the web-server (http://localhost:80) when processing to
inject via POST method manipulated `filenames`. The file name will be changed to the path value without secure filter,
encode or parse. The injected script code occurs in the folder listing of the file location in the separate path.
Exploitation of the persistent web vulnerability requires low user interaction and a local low privilege mobile application account.
Successful exploitation of the vulnerability can lead to persistent session hijacking (customers), account steal via persistent
web attacks, persistent phishing or persistent module context manipulation.
Vulnerable Application(s):
[+] Phone Drive v3.0.3 - ITunes or AppStore (Apple)
Vulnerable Module(s):
[+] File Listing - Names
Vulnerable Parameter(s):
[+] rename (filename)
Affected Module(s):
[+] File Listing (INDEX & SUB CATEGORIES)
Proof of Concept (PoC):
=======================
1.1
The local command/path inject web vulnerability can be exlploited by local attackers with physical iOS device access and user interaction.
For demonstration or reproduce ...
PoC: Listing (INDEX & SUB CATEGORIES) - INJECT via Device Name
<tr>
<td><a href="./"><img src="/webroot/webicon.png" id="headerImg" height="57" width="57"></a></td>
<td><h2>iPad ¥337 360*[LOCAL COMMAND/PATH INJECT VULNERABILITY]</h2></td>
<td align="center" width="170"><a href="http://www.eightythreetech.com" target="_blank">
<img src="/webroot/moreapps.png"></a></td></tr>
Manual steps to reproduce the vulnerability ...
1. Download the Phone Drive application to your iOS test device
2. Login to your ipad install and startup the software
3. Open the iOS settings of your iphone or ipad and change the device (system) name to your script code with local path and or command var
4. Save the input and start sharing the files with the iOS app
5. Open as localhost the service in your browser to request the http web server
6. The command/path inject will be executed in the header location of the app web-server index and also in all sub categories
7. Successful reproduced!
1.2
The local command/path inject web vulnerability can be exlploited by remote attackers without privilege application user account
and user interaction. For demonstration or reproduce ...
--- Request Session Log (POST METHOD) ---
Status: 200[OK]
POST http://192.168.2.104/#
Load Flags[LOAD_DOCUMENT_URI LOAD_INITIAL_DOCUMENT_URI ]
Content Size[5458]
Mime Type[application/x-unknown-content-type]
Request Headers:
Host[192.168.2.104]
User-Agent[Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Firefox/22.0]
Accept[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8]
Accept-Language[en-US,en;q=0.5]
Accept-Encoding[gzip, deflate] DNT[1]
Referer[http://192.168.2.104/]
Connection[keep-alive]
Post Data:
createFolder[Benjamin%2520%3E%3C(LOCAL COMMAND/PATH INJECT VULNERABILITY)ios]
ID[0]
submitButton[Create]
Response Headers:
Accept-Ranges[bytes]
Content-Length[5458]
Date[Tue, 30 Jul 2013 16:16:47 GMT]
PoC: Listing (INDEX & SUB CATEGORIES) - INJECT via Creat/Add Foldername
<form name="checkbox_form"></form>
<tr><td class="e"><input name="selection" value="Benjamin%2520%3E%3Ciframe%20src=a%3Ebkm37ios"
type="checkbox"></td><td class="i"><a href="Benjamin%2520%3E%3Ciframe%20src=a%3Ebkm37ios/"><img src="/webroot/fileicons/folder.png"
height="20" width="20"></a></td>
<td class="n"><a href="Benjamin%2520%3E%3C[LOCAL COMMAND/PATH INJECT VULNERABILITY]ios/">Benjamin%20>
<[LOCAL COMMAND/PATH INJECT VULNERABILITY]ios
</a></td><td class="m">
Note:
To reproduce the inject of the command/path request with script code inject the payload inside of the foldername input on creat or edit.
The code will be executed in the index foldername listing and in the sub category and foldername listing.
1.3
The persistent input validation web vulnerability can be exploited by remote attackers without privilege application user account and
low user interaction. For demonstration or reproduce ...
--- Request Session Log (POST METHOD) ---
Status: 200[OK]
POST http://192.168.2.104/Benjamin%2520%3E%3Cbkm37%3Ebkm37ios/#
Load Flags[LOAD_DOCUMENT_URI LOAD_INITIAL_DOCUMENT_URI ]
Content Size[4837]
Mime Type[application/x-unknown-content-type]
Request Headers:
Host[192.168.2.104]
User-Agent[Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Firefox/22.0]
Accept[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8]
Accept-Language[en-US,en;q=0.5]
Accept-Encoding[gzip, deflate] DNT[1]
Referer[http://192.168.2.104/Benjamin%2520%3E%3Cbkm37%3Ebkm37ios/]
Connection[keep-alive]
Post Data:
renameFile[%3C(PERSISTENT INJECTED SCRIPT CODE!)%3Eintro.png]
ID[intro.png]
submitButton[Rename]
Response Headers:
Accept-Ranges[bytes]
Content-Length[4837]
Date[Tue, 30 Jul 2013 16:39:10 GMT]
PoC: Listing (File Name) - INJECT via Rename Files Function
<tr><td class="e"><input name="selection" value="%3C[PERSISTENT INJECTED SCRIPT CODE!]%3Eintro.png"
type="checkbox"></td><td class="i"><a href="%3C[PERSISTENT INJECTED SCRIPT CODE!]%3Eintro.png">
<img src="/webroot/fileicons/png.png" height="20" width="20"></a></td><td class="n">
<a href="%3C[PERSISTENT INJECTED SCRIPT CODE!]%3Eintro.png"><[PERSISTENT INJECTED SCRIPT CODE!]">intro.png</a></td>
<td class="m">30.07.2013 18:38</td>
<td class="s">17.9 KB</td><td class="k">Portable Network Graphics Image</td><td class="e"><a href="#"
title="Download file" onClick="downloadFile("%3C[PERSISTENT INJECTED SCRIPT CODE!]%3Eintro.png");">
<img src="/webroot/webdownload.png" width="15" height="15"/></a></td><td class="e"><a href="#"
title="Rename file" onClick="modalPopup("%3C[PERSISTENT INJECTED SCRIPT CODE!]%3Eintro.png", 0, 0);">
<img src="/webroot/webrename.png" width="15" height="15"/></a></td><td class="e"><a href="#"
title="Delete file" onClick="modalPopup("%3C[PERSISTENT INJECTED SCRIPT CODE!]%3Eintro.png", 2, 0);">
<img src="/webroot/webdelete.png" width="15" height="15"/></a></td></tr>
</form>
</tbody>
</table>
</div>
Security Risk:
==============
1.1
The security risk of the local command/path inject vulnerability is estimated as high(-).
1.2
The security risk of the security command/path inject vulnerability is estimated as high(+).
1.3
The security risk of the persistent input validation web vulnerability in the file names is estimated as high.
Credits & Authors:
==================
Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri ([email protected])
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: [email protected] - [email protected] - [email protected]
Section: www.vulnerability-lab.com/dev - forum.vulnerability-db.com - magazine.vulnerability-db.com
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
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 ([email protected] or [email protected]) to get a permission.
Copyright © 2013 | Vulnerability Laboratory [Evolution Security]
Data
Build on a solid foundation with Vulners data
We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data
Api
Power your application with Vulners API
The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access
App
Assess and manage vulnerabilities with Vulners tools
Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation