The Android app Web Explorer – Fast Internet left an open instance, exposing a trove of sensitive data that malicious actors could use to check specific users’ browsing history.
Original post at https://cybernews.com/security/android-app-leaked-user-browsing-history/
A browsing app for Android devices, Web Explorer – Fast Internet, left open its Firebase instance, exposing app and user data, the Cybernews research team has discovered.
Firebase is a mobile application development platform that offers many features, including analytics, hosting, and real-time cloud storage.
Web Explorer – Fast Internet is a browsing app with over five million downloads on the Google Play store. It boasts of increasing browsing speed by 30% and has a user rating average of 4.4 out of five stars, across more than 58,000 reviews.
De-anonymize users
According to the team, the open Firebase instance contained days’ worth of redirect data, presented by user ID. This included country, redirect initiating address, redirect destination address, and user country.
“If threat actors could de-anonymize the app’s users, they would be able to check a bunch of information on browsing history for a specific user and use it for extortion,” Cybernews researchers said.
However, getting their hands on the data that Web Explorer – Fast Internet left exposed would not be enough by itself. A threat actor would also have to seek out where app developers store additional user data. That said, cross-referencing the leaked data with additional details could amplify any damage done to the app’s users.
Keys and IDs
The team also discovered that the app had hardcoded sensitive information on the client side of the application. Hardcoding sensitive information, commonly known as “secrets,” is considered a bad practice as threat actors could extract it for malicious use.
Web Explorer – Fast Internet had a hardcoded firebase_database_url key that points to a database with anonymized partial user browsing history, default_web_client_id, a unique public identifier dispatched for an application using Firebase, gcm_defaultSenderId, a key enabling cross-server communication.
“If threat actors could de-anonymize the app’s users, they would be able to check a bunch of information on browsing history for a specific user and use it for extortion.”Cybernews researchers said.
The app also held google_api_key and google_api_id, both used for authentication purposes. API Key and app ID are used to identify a verified Google app to access Google API services.
Additionally, the team found google_crash_reporting_key and google_storage_bucket key hardcoded in the app. The first key is not considered too sensitive, but threat actors can still exploit it to impact user experience. For example, they could issue mock requests, disrupting the app’s crash-reporting and negatively affecting performance.
Meanwhile, leaving the google_storage_bucket_key hardcoded in the app allows threat actors to read and write any information on the dedicated bucket in the Google Cloud Service (GCS) if the bucket lacks authorization setup. Even though the team did not check whether the bucket was publicly accessible, it is still a misconfiguration case that could lead to sensitive user details being further exposed.
Is it solved now?
The team reached out to Web Explorer but …. give a look at the
Original post at https://cybernews.com/security/android-app-leaked-user-browsing-history/
About the author Vilius Petkauskas, Senior Journalist
Follow me on Twitter: @securityaffairs and Facebook and Mastodon
|
try { window._mNHandle.queue.push(function (){ window._mNDetails.loadTag(“816788371”, “300×250”, “816788371”); }); } catch (error) {}
try { window._mNHandle.queue.push(function (){ window._mNDetails.loadTag(“816788371”, “300×250”, “816788371”); }); } catch (error) {}
|
(SecurityAffairs – hacking, Android app)
The post <strong>Android app with over 5m downloads leaked user browsing history</strong> appeared first on Security Affairs.
