iClassSchedule 1.6 iOS & Android - Persistent UI Vulnerability
Vulnerability Laboratory ID (VL-ID):
Common Vulnerability Scoring System:
Product & Service Introduction:
Couldn`t you remember your lesson time? If you are a high-school student or a university one, you will be able easily to consult your weekly guide,
using this App on your iPhone. You could choose your sujects following your plan and give them a colour for marking them at the end of the week.
(Copy of the Homepage: https://play.google.com/store/apps/details?id=com.idalmedia.android.
timetable&hl=it & https://itunes.apple.com/en/app/orariolezioni/id542313616)
Abstract Advisory Information:
The Vulnerability Laboratory Research Team discovered a persistent input validation vulnerability in the official iClassSchedule v1.6 iOS & Android mobile web-application.
Vulnerability Disclosure Timeline:
2015-05-13: Public Disclosure (Vulnerability Laboratory)
Product: iClassSchedule - iOS & Android Mobile Web Application 1.6 iOS and 4.6 Android
Technical Details & Description:
An application-side validation vulnerability has been discovered in the official iClassSchedule v1.6 iOS & Android mobile web-application.
The vulnerability allows an attacker to inject own script code as payload to the application-side of the vulnerable service function or module.
The vulnerability is located in the `Aula (name input)` values of the vulnerable `iClass Calender` module. Local attackers are able to manipulate
the `Aula name` input to compromise the `Calender Index` module. The execution point of the script code occurs on the application-side in the
listing module by the manipulated name context field. The Apple iOS and Google Android mobile application versions are affected by the vulnerability.
The security risk of the application-side web vulnerability is estimated as medium with a cvss (common vulnerability scoring system) count of 3.4.
Exploitation of the application-side web vulnerability requires a privileged web-application user account and low or medium user interaction.
Successful exploitation of the vulnerabilities result in persistent phishing mails, session hijacking, persistent external redirect to malicious
sources and application-side manipulation of affected or connected module context.
[+] iClass Calender Events Context (App Index)
Proof of Concept (PoC):
The persistent input validation web vulnerability can be exploited by local attackers with physical device access and with low user interaction.
For security demonstration or to reproduce the security vulnerability follow the provided information and steps below to continue.
1. Install the mobile application to your iOS or Android device
2. Open the application and add a new entry to the iclass calender index
3. Inject to the Aula name value your own script code (payload) for testings
4. Save the entry and move back to the iclass calender index of the app
5. The code executes because of the wrong encoding in the calender itself.
Note: Export and Exchange of malicious context is possible!
6. Successful reproduce of the security vulnerability!
Solution - Fix & Patch:
The vulnerability can be patched by a secure parse and encode of the vulnerable name value in the iclass calender module.
Restrict the name input and disallow usage of special chars to prevent persistent cross site scripting attacks.
The security risk of the persistent input validation web vulnerability in the name value is estimated as medium. (CVSS 3.4)
Credits & Authors:
Vulnerability Laboratory [Research Team] - Katharin S. L. (CH) ([email protected]) [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: [email protected] - [email protected] - [email protected]
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 protected] or [email protected]) to get a permission.
Copyright © 2015 | Vulnerability Laboratory - [Evolution Security GmbH]™
-- VULNERABILITY LABORATORY - RESEARCH TEAM SERVICE: www.vulnerability-lab.com CONTACT: [email protected] PGP KEY: http://www.vulnerability-lab.com/keys/admin@vulnerability-lab.