FCS Scanner v1.0 & v1.4 - Command Inject Vulnerability
Vulnerability Laboratory ID (VL-ID):
Common Vulnerability Scoring System:
Product & Service Introduction:
This app (available in German and English) scans your smartphone or tablet and supplies you with detailed hardware and software information.
All data can be sent by mail in xml format. For an exact identification of every mobile: the name of the file attached contains the inventory
number, if there is one, or the Serial Number otherwise. Thus you can do a professional inventory for multiple phones or tablets!
(Copy of the Homepage: https://itunes.apple.com/nz/app/fcs-scanner/id902969515 & https://play.google.com/store/apps/details?id=fcs.apps.fcsscanner )
Abstract Advisory Information:
The Vulnerability Laboratory Research team discovered a local command inject web vulnerability in the official FCS Scanner v1.0 iOS & v1.4 Android mobile application.
Vulnerability Disclosure Timeline:
2015-06-30: Public Disclosure (Vulnerability Laboratory)
FCS Fair Computer Systems GmbH
Product: FCS Scanner - iOS & Android Mobile Application 1.0 & 1.4
Technical Details & Description:
A local command inject web vulnerability has been discovered in the official FCS Scanner v1.0 iOS & v1.4 Android mobile application.
The vulnerability allows to inject malicious script codes on the application-side of the vulnerable mobile fcs scanner app.
The vulnerability is located in the device id value of the send by mail function. Local attackers are able to manipulate the name value
of the device to compromise the mail function of the fcs scanner mobile app. The html and xml encoding is broken in the send by mail
export function. Local attackers are able to manipulate the device name id to compromise the application internal validation in the send
emails module. The attack vector of the vulnerability is server-side and the injection point is the device name information settings.
The security risk of the local command/path inject vulnerability is estimated as medium with a cvss (common vulnerability scoring system) count of 5.9.
Exploitation of the command/path inject vulnerability requires a low privilege android/ios device account with restricted access and no user interaction.
Successful exploitation of the vulnerability results in unauthorized execution of system specific commands and unauthorized path value requests to
compromise the mobile iOS application and connected device components.
[+] Device - Settings - Information
[+] device id
[+] FCS Scanner - Mail & XML
Proof of Concept (PoC):
The local command inject web vulnerability can be exploited by local attackers with low privilege device user account and without 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. Start the iOS device
2. Open the settings module
3. Change the name to the local command injection payload
4. Save the settings and start the application fcs scanner
5. Send the details by mail
6. Review the arrival inbox
7. The execution point is the xml and header location with the device id value
8. Successful reproduce of the local command inject security vulnerability!
PoC: Device ID - Email
Device ID: bkm337>"<./[LOCAL COMMAND INJECT VULNERABILITY VIA DEVICE NAME VALUE!] src"x"="" src="cid:">>
Serial No: FB9BA2FF-5F09-4D67-9EDF-DF619C8FC6AE
PoC: XML - fcs-FB9BA2FF-5F09-4D67-9EDF-DF619C8FC7EA
Solution - Fix & Patch:
The vulnerability can be patched by a secure parse and encode of the vulnerable Device ID value. Restrict the input and encode the output in the
vulnerable generated xml file.
Disallow script code values in the html generated xml file type to prevent further command injection attacks.
The security rsik of the local command inject web vulnerability in the device cell name is estimated as medium. (CVSS 5.9)
Credits & Authors:
Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri (email@example.com) [www.vulnerability-lab.com]
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: firstname.lastname@example.org - email@example.com - firstname.lastname@example.org
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
(email@example.com or firstname.lastname@example.org) to get a permission.
Copyright © 2015 | Vulnerability Laboratory - [Evolution Security GmbH]™