← Back to index
References / filed

CHANGE_WIFI_STATE

Can toggle WiFi, start scans, and add networks. A normal permission, which makes it easy to overlook in an otherwise loud manifest.

258 words2 min read
Filed under
#android#permissions#reference

Granted automatically at install, no runtime prompt. CHANGE_WIFI_STATE is the write counterpart to ACCESS_WIFI_STATE: it lets an app enable or disable WiFi, initiate scans, and add or modify network configurations.

The detail that makes it worth a second look is adding networks. An app holding this can programmatically join the device to a network without the owner choosing it, which is a genuine capability rather than a convenience. Disabling WiFi on its own is mostly nuisance behaviour, and can even be read as self-defeating for malware that needs to reach its command server.

No traced use appears in the write-up's findings. Unlike the telephony permissions, where the analysis names the classes and endpoints consuming them, the WiFi and network-state permissions show up as manifest declarations without code-level behaviour behind them. On their own they read as a background-capability group the template declares for completeness, alongside the persistence permissions and the account recon block.

All three are normal permissions, granted at install, so none of them contributes a visible signal to someone reviewing the permission screen on the device.

Both WiFi permissions being normal is the part that makes the pair easy to miss. Neither appears in the consent dialog, so a reviewer reading the dangerous list alone would conclude the app cannot touch connectivity, which is wrong.

Related: ACCESS_WIFI_STATE, ACCESS_NETWORK_STATE

Part of Few Android permissions I have seen used often. All permissions here were seen in the mprivhaan analysis.