Title: ====== eTransfer Lite v1.0 iOS - Persistent Filename Vulnerability Date: ===== 2013-08-31 References: =========== http://www.vulnerability-lab.com/get_content.php?id=1064 VL-ID: ===== 1064 Common Vulnerability Scoring System: ==================================== 3.8 Introduction: ============= eTransfer is a tool for you to transfer photos among pc, iPad. eTransfer does not need iTunes. It supports to transfer photo: - iPad to iPad - iPad to PC - PC to iPad eTransfer does not need extra software. All you need is the device that installed eTransfer and web browser on any os. (Copy of the Homepage: https://itunes.apple.com/de/app/etransfer-lite-for-ipad/id492163598 ) Abstract: ========= The Vulnerability Laboratory Research Team discovered a persistent web vulnerability in the eTransfer Lite v1.0 application (Apple iOS - iPad & iPhone). Report-Timeline: ================ 2013-08-31: Public Disclosure (Vulnerability Laboratory) Status: ======== Published Affected Products: ================== Apple AppStore Product: eTransfer Lite 1.0 Exploitation-Technique: ======================= Remote Severity: ========= Medium Details: ======== A persistent input validation web vulnerability is detected in the eTransfer Lite v1.0 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 `Receive Photos from others` and `Send Photos to others` module of the web-server (http://localhost:8080) when processing to request via POST method manipulated `file-names`. The file name will be changed to the path value without secure filter, encode or parse. The injected script code will be executed in the main file listing were the attacker injected earlier the code and of course also in the index listing of the mobile web application. There is a security protection to filter random files because only images are allowed. To include own script code the attacker needs to manipulate the POST request after the first separate input parse. Exploitation of the persistent web vulnerability requires low user interaction and a local low privilege mobile application account with a password. 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): [+] eTransfer Lite v1.0 - ITunes or AppStore (Apple) Vulnerable Module(s): [+] File Listing Vulnerable Parameter(s): [+] file name Affected Module(s): [+] Index File Dir & Path Listing [+] Path/Folder Listing Proof of Concept: ================= The persistent input validation web vulnerability can be exploited by remote attackers and local privileged application user accounts with low or medium user interaction. For demonstration or reproduce ... PoC: <bq>The following files are hosted live from the iPad's Docs folder.</bq><p><b>Images:<br><br></b> <a href="http://192.168.2.104:8080/%3C[PERSISTENT INJECTED SCRIPT CODE!]%3Es2.png"><[PERSISTENT INJECTED SCRIPT CODE!]">s2.png</a> ( 51.8 Kb, 2013-08-25 02:09:25 +0000)<br /> <a href="a2b642e7de.jpg">a2b642e7de.jpg</a> ( 238.0 Kb, 2013-08-25 02:08:13 +0000)<br /> </p><br><br><br><hr><br><br><br><center><form action="" method="post" enctype="multipart/form-data" name="form1" id="form1"><label>Upload file to iPad <input type="file" name="file" id="file" /></label><label> <input type="submit" name="button" id="button" value="Submit" /></label></form></center><br><br><br>Powered By <a href=http://www.kaisatec.com>Kaisatec.com</a></body></html></iframe></a></p></body></html> Reference(s): http://localhost:8080/ Solution: ========= To fix the vulnerability the filename needs to be parsed, escaped or separate encoded in the POST method request. Parse also the affected output listing in the of the filename in the index file dir listing and sub category path folder listing. Risk: ===== The security risk of the persistent input validation web vulnerability is estimated as medium(+). Credits: ======== Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri (bkm@evolution-sec.com) [www.vulnerability-lab.com] Disclaimer: =========== 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: 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 (admin@vulnerability-lab.com or research@vulnerability-lab.com) to get a permission. Copyright &#169; 2013 | Vulnerability Laboratory [Evolution Security] -- VULNERABILITY LABORATORY RESEARCH TEAM DOMAIN: www.vulnerability-lab.com CONTACT: research@vulnerability-lab.com