Vulnerability Note VU#439016
TaxiHail Android mobile app contains multiple vulnerabilties
Original Release date: 08 Dec 2015 | Last revised: 08 Dec 2015
Mobile Knowledge’s TaxiHail is vulnerable to information disclosure and missing encryption of sensitive data.
The Mobile Knowledge TaxiHail framework "allows passengers to book and manage their own reservations via iOS, android or the web in real-time, alleviating call congestion during peak busy hours."
TaxiHail prior to version 3.1.26 has been reported vulnerable to the following issues:
CWE-276: Incorrect Default Permissions
TaxiHail creates a log file that contains the GPS information about the user. The log file does not contain proper permissions, allowing other apps to read the log’s location data.
CWE-311: Missing Encryption of Sensitive Data
TaxiHail does not use encryption when communicating with the server.
TaxiHail can be customized for deployment by taxi companies, meaning that multiple apps available via the iOS and Google app stores may inherit this vulnerability. According to the reporter, "over 100" apps may derive from TaxiHail.
An unauthenticated remote attacker may be able to gain private knowledge of the app user, and sniff network traffic from the app.
Apply an update
Mobile Knowledge has addressed this issue in version 3.1.26 of the TaxiHail app for both Android and iOS. Apps making use of TaxiHail have also been regenerated.
An older version of TaxiHail was reported as not correctly validating SSL certificates. According to the reporter, this issue is fixed in the latest version of TaxiHail. It is currently unclear which version originally addressed this problem.
Affected users should update their apps as soon as possible to obtain the fix.
Vendor Information (Learn More)
VendorStatusDate NotifiedDate UpdatedMobile KnowledgeAffected-08 Dec 2015If you are a vendor and your product is affected, let
CVSS Metrics (Learn More)
Thanks to the Shaftek Security Research Team for reporting this vulnerability.
This document was written by Garret Wassermann.
08 Dec 2015
Date First Published:
08 Dec 2015
Date Last Updated:
08 Dec 2015
FeedbackIf you have feedback, comments, or additional information about this vulnerability, please send us email.