← Back to index
References / filed

READ_SYNC_SETTINGS

Reads Android's account sync configuration, which maps the victim's sync environment without touching any synced content.

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

Granted automatically at install, and one of five that the mprivhaan kit declares as a block alongside READ_SYNC_STATS, WRITE_SYNC_SETTINGS, GET_ACCOUNTS, and AUTHENTICATE_ACCOUNTS. Reading it gives an app visibility into how account synchronisation is configured on the device: which account types exist, which sync adapters are enabled, and how the system is set up to move data in the background.

The important limitation is what it does not do. READ_SYNC_SETTINGS is not access to the content being synchronised. It tells you about the plumbing, not the payload. On its own that is reconnaissance-grade information, not a data breach.

Read as part of a set, though, it becomes something else. Paired with GET_ACCOUNTS it maps which services the victim actually uses. Paired with READ_SYNC_STATS it reveals whether those services have been syncing, and how much. And paired with WRITE_SYNC_SETTINGS the set stops being read-only, which is what READ_SYNC_STATS and WRITE_SYNC_SETTINGS cover in turn.

None of the five touches synced content directly, which is probably why they are easy to dismiss. But together they amount to a full account-recon capability: the app knows what accounts exist, knows how they are configured, can observe their sync activity, and can change their sync settings. That is enough to understand the victim's device before stealing anything from it, and it is a plausible template artefact rather than a feature the payload actively drives.

Related: WRITE_SYNC_SETTINGS, READ_SYNC_STATS, GET_ACCOUNTS

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