BUG BOUNTYFIELD MANUAL
Vulnerability reference
Markdown
0 / 5 checkedChecks last until this page reloads.

Private client content leaks through a lower-trust display or sharing channel

A private marker appears in a notification, background snapshot, clipboard or another user-visible channel outside its promised audience.

Candidate CWE: Map the actual root cause once established.

Test hypothesis#

Seed a private/public fixture pair and compare lock, background and account-switch states through the normal OS UI. Obtain the marker with only the stated observer privileges.

Evidence required#

Capture exact app/OS version, privacy settings, content ownership, reader prerequisites, state transition and the smallest marker exposure. Classify the actual display, notification, clipboard or sharing-channel mechanism; confidentiality loss alone does not establish a specific CWE root cause.

Rule out false positives#

Missing screenshot flags, intended account-owner display, explicitly granted accessibility authority, or a deliberate user-enabled notification preview may not violate the product's security contract.

Playbook and command references#

Find the associated command snippets

Referenced by these target playbooks#

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.

Primary references#

Back to the complete vulnerability catalog