WiFly 1.0 Pro iOS - Multiple Vulnerabilities
WiFly 1.0 Pro iOS - Multiple Web Vulnerabilities
Common Vulnerability Scoring System:
It is the best solution for transferring photos, songs, documents, movies and other files between computer
and your mobile devices over wireless network. Simply launch application on your iOS device and scan QR
code from http://wifly.me to connect your phone. Drop your files into opened page and vice versa!
No cloud or internet access required - no data leaves your local network. Both your devices must have access
to the same LAN or WLAN - no additional network configurations needed. Transferred documents can be opened with
any supported App on your iOS device.
- Multiple uploads
- Easily Drag & Drop multiple files to WiFly
- Preview pictures in the browser
- Downloading the entire folder to your computer
- Browsing files and folders directly on mobile device
- Exchange files between mobile devices
- Built in preview of images, documents, music and video files
(Copy of the Homepage: https://itunes.apple.com/us/app/wifly-pro/id641092695 )
The Vulnerability Laboratory Research Team discovered multiple vulnerabilities in the WiFly 1.0 Pro application (Apple iOS - iPad & iPhone).
2013-07-15: Public Disclosure (Vulnerability Laboratory)
Product: WiFly Pro 1.0
A local file include and arbitrary file upload web vulnerability is detected in the WiFly 1.0 Pro application (Apple iOS - iPad & iPhone).
The vulnerabilities are located in the file upload module of the web-server (http://localhost:4885/) when processing
to request via POST a manipulated filename. The injected file will be accessable via the index listing module of the application.
Remote attackers can exchange the filename with a double or tripple extension via POST method to bypass the upload validation and filter process.
After the upload the attacker access the file with one extension and exchange it with the other one to execute for example php, js, html codes.
The filter in the application itself disallow to rename a file with special chars because of a input field restriction. Attackers need to request
2 different urls. First the file as url with a parameter of the filename inside to display and as secound step the file will be uploaded with
the manipulated filename in the POST request.
Exploitation of the vulnerability requires no user interaction but the victim iOS device needs to accept the other device connection.
Successful exploitation of the vulnerability results in unauthorized path or file access via local file include or arbitrary file upload.
[+] WiFly Pro 1.0 - ITunes or AppStore (Apple)
[+] upload.json & add
[+] Index Listing (http://localhost:4885/)
Proof of Concept:
The local file/path include and arbitrary file upload vulnerability can be exploited by remote attackers without user interaction
but the connection needs to be accepted by the target system. For demonstration or reproduce ...
Content-Disposition: form-data; name="files"; filename="s2.png"\r\nContent-Type: image/png\r\n\r\n?PNG\r\n\n
Load Flags[LOAD_BYPASS_CACHE ] Content Size Mime Type[application/x-unknown-content-type]
PoC: 1.1 - File/Path Include Vulnerability
last_modified=1331091664536000&name=../../[File/Path Include Vulnerability!].png&sessionid=1373658611109
Content-Disposition: form-data; name="files"; filename="../../[File/Path Include Vulnerability!]"
PoC: 1.2 - Arbitrary File Upload Vulnerability
last_modified=1331091664536000&name=[Arbitrary File Upload Vulnerability!].png.gif.html.php.js&sessionid=1373658611109
Content-Disposition: form-data; name="files"; filename="[Arbitrary File Upload Vulnerability!].png.gif.html.php.js"
The vulnerability can be patched by a restriction of the json upload request and url parameter.
The POST request when processing to upload needs to be restricted, encoded and filtered.
The security risk of the local file/path include & arbitrary file upload vulnerability is estimated as high.
Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri (email@example.com)
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: firstname.lastname@example.org - email@example.com - firstname.lastname@example.org
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@example.com or firstname.lastname@example.org) to get a permission.
Copyright � 2013 | Vulnerability Laboratory [Evolution Security]
VULNERABILITY LABORATORY RESEARCH TEAM