# Backup or transfer exposes unintended sensitive client state

A supported backup, migration or diagnostic-copy path carries a secret into an unintended recipient or security context.

**Candidate CWE:** [CWE-530](https://cwe.mitre.org/data/definitions/530.html) · [CWE-922](https://cwe.mitre.org/data/definitions/922.html)

## Test hypothesis

Seed one owned secret, run the supported backup/restore or export workflow, then check whether an explicitly excluded item becomes usable in the destination. Compare a session-free baseline.

## Evidence required

OS/build, actual backup channel and rules, restored marker, recipient privileges and any scoped demonstration that recovered authorization remains usable.

## Rule out false positives

Backup enabled alone is insufficient. Account-owner migration may be intended; Android cloud and device-transfer behavior can differ.

## Playbook and command references

- [Client storage, logs, backup and transport trust](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/modules/client-storage-transport.html) — Measure where sensitive client state goes, who can retrieve it, and whether transport rejects invalid peers.
- [Authentication, recovery, federation, and session lifecycle](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/modules/identity-session.html) — Test registration, recovery, identity changes, invitations, SSO enforcement, and deprovisioning as one account state machine.

[Find the associated command snippets](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/commands.html?q=Client%20storage%2C%20logs%2C%20backup%20and%20transport%20trust)

## Referenced by these target playbooks

[Mobile](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/mobile.html) · [Desktop & extensions](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/desktop.html)

## Report checklist

- [ ] Capture the affected version, configuration, identities, and object ownership.
- [ ] Preserve a valid baseline and a negative control.
- [ ] Reproduce the forbidden data access, action, or state change on controlled fixtures.
- [ ] Explain the intended security rule and why the observed behavior violates it.
- [ ] State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.

## Conditional ATT&CK mapping

No direct ATT&CK mapping selected. Record the weakness and demonstrated impact without forcing an adversary-behavior classification. See the [mapping guide](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/attack.html).

## Primary references

- [Android Auto Backup](https://developer.android.com/identity/data/autobackup)

[Back to the complete vulnerability catalog](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/vulnerabilities.html)