Tuesday, March 4, 2025
HomeAndroidWiFi Broadcasts in All Version of Android OS Leaking Sensitive Data Including...

WiFi Broadcasts in All Version of Android OS Leaking Sensitive Data Including IP Addresses, BSSID, WiFi Network Name

Published on

SIEM as a Service

Follow Us on Google News

WiFi Broadcasts in Android OS Leaking sensitive data from a user’s Android device and the details about all the application that running on the user’s device.

All the version of Android running devices is affected by this vulnerability including  Amazon’s FireOS for the Kindle.

It leaks Sensitive information such as WiFi network name, BSSID, local IP addresses, DNS server information and the MAC address.

Other than this, attackers need some extra permission to access the rest of the information in the vulnerable Android devices.

Since the MAC address unique for every Android mobile and its tied to hardware thus helps to track any Android device.

Apart from this, network name and BSSID can be used to geolocate users via a lookup against a database of BSSID such as WiGLE or SkyHook.

WiFi Broadcasts Vulnerability Analysis

Android using service called  “Intents” for interprocess communication, also in order to send a message by application or OS that can be listed by other applications  “Intent” is mainly used by broadcast.

Also, it restricts who is allowed to read such messages or mask sensitive data. along with this Another security mechanism present in the Android is permissions that used to protect the privacy of users.

There are 2 intents used by Android OS broadcasts about WiFi connection and the WiFi network interface.

According to nightwatch cybersecurity, on Android versions 6.0 and later, the real MAC address of the device is no longer available via APIs and will always return the address “02:00:00:00:00:00”. However, an application listening for system broadcasts does not need these permissions thus allowing this information to be captured without the knowledge of the user and the real MAC address being captured even on Android 6 or higher.

In this behavior has been confirmed in multiple types of hardware and Android versions. For Android device users, you can replicate these issues as follows:

  1. Install the “Internal Broadcasts Monitor” application developed by Vilius Kraujutis from Google Play.
  2.  Open the application and tap “Start” to monitor broadcasts.
  3.  Observe system broadcasts, specifically “android.net.wifi.STATE_CHANGE” and “android.net.wifi.p2p.THIS_DEVICE_CHANGED”.

This is has been reported to Google and they fixed the vulnerability in Android P / 9. The vendor does not plan to fix prior versions of Android. Users are encouraged to upgrade to Android P / 9 or later.

References

Android ID # 77286245
CVE ID: CVE-2018-9489
Google Bug # 77236217
GitHub: Internal Broadcasts Monitor

Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Latest articles

Bubba AI, Inc. is Launching Comp AI to Help 100,000 Startups Get SOC 2 Compliant by 2032.

With the growing importance of security compliance for startups, more companies are seeking to...

IBM Storage Virtualize Flaws Allow Remote Code Execution

Two critical security flaws in IBM Storage Virtualize products could enable attackers to bypass...

Progress WhatsUp Gold Path Traversal Vulnerability Exposes Systems to Remote code Execution

A newly disclosed path traversal vulnerability (CVE-2024-4885) in Progress Software’s WhatsUp Gold network monitoring...

CISA Alerts on Active Exploitation of Cisco Small Business Router Flaw

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) issued an urgent warning on March...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

IBM Storage Virtualize Flaws Allow Remote Code Execution

Two critical security flaws in IBM Storage Virtualize products could enable attackers to bypass...

Progress WhatsUp Gold Path Traversal Vulnerability Exposes Systems to Remote code Execution

A newly disclosed path traversal vulnerability (CVE-2024-4885) in Progress Software’s WhatsUp Gold network monitoring...

CISA Alerts on Active Exploitation of Cisco Small Business Router Flaw

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) issued an urgent warning on March...