ALERT: Truecaller Bug Leaves Millions of Android Devices Vulnerable, are you at risk?

Recently, security researchers from the Cheetah Mobile Security Research Lab discovered a loophole in the popular phone call management application Truecaller.

This vulnerability, which has been fixed in the latest Android update, could have allowed anyone to potentially gain access to Truecaller users’ information and change their call blocking settings. The millions of Android users who downloaded this app on their smartphones could be in danger.

The CM Security Research Lab recommends that Truecaller Android users update to the latest version on Google Play immediately.

The researcher found that Truecaller uses devices’ IMEI as the only identity label of its users. Meaning that anyone gaining the IMEI of a device will be able to get Truecaller users’ personal information (including phone number, home address, mail box, gender, etc.) and tamper app settings without users’ consent, exposing them to malicious phishers.

By exploiting this flaw, the attackers can:

  • Steal personal information like account name, gender, e-mail, profile pic, home address, etc.

  • Modify a user’s application settings:

  • Disable spam blockers

  • Add to a black list for users

  • Delete a user’s blacklist

The Cheetah Mobile Security Research Team notified the developer of Truecaller about this vulnerability as soon as they discovered the loophole and offered all it could to help the developer fix the issue. Now the maker of Truecaller has addressed the issue and released an update on March 22nd.

Although the flaw has been fixed in the latest version, the majority of the users are still in danger as they have not got access to the new release yet. The CM Security Research Lab advises Truecaller users to upgrade this app to the latest version as soon as possible.

Update: Truecaller has issued a Security Update Notification about the fix. You can read the details at http://blog.truecaller.com/security-update-notification/.

———–
Source: https://www.cmcm.com/blog/en/security/2016-03-28/974.html

Leave a Reply