vulns.co
/
GKData.io MCP and API Buy me a coffee

Apple · Authorization and tenant boundaries

Sign in with Apple failed to bind identity claims to the authenticated user

Sign in with Apple did not reliably check that identity claims belonged to the signed-in user, putting some third-party accounts at risk. Bhavuk Jain reports a $100,000 payment; he did not test the named third-party applications. USD is inferred from Apple's May 2019 program documentation, about a year before the May 2020 disclosure.

Read the original writeupUSD 100,000 reported award · Reviewed 2026-10-04

Root cause

Token issuance did not reliably bind identity claims to the authenticated user. A relying application could receive a cryptographically valid token whose claims did not belong to that user. Checking the token’s cryptography alone could not establish claim ownership.

Demonstrated impact

Potential takeover of third-party application accounts using the integration without additional safeguards. Named third-party applications were not tested by the researcher.

What to check for

  • Validate identity-claim ownership in addition to token cryptographic validity.
  • Document relying-party assumptions and additional authentication safeguards.

Award and evidence

USD 100,000Bug Bounty · Researcher Reported
How the award was verified, and what the record does not establish

The researcher explicitly reports being paid $100,000 but supplies no currency code or exact settlement date. USD is contextually inferred from Apple's May 2019 iOS Security guide (currency-context), whose Apple Security Bounty table on printed page 87 labels maximum payments in USD. This source describes the then-existing iOS program and predates the May 2020 disclosure by about one year. It supplies denomination context only and does not independently establish this individual payment's currency, amount, category or settlement.

  • No exact report, fix, or payment date stated
  • Researcher says Apple's investigation found no misuse; independent vendor payout confirmation was not retrieved
  • USD is inferred from earlier program-level context, not explicitly stated in the individual payment report. The May 2019 guide does not establish the payment's category or the program wording at payment time. No conflicting denomination was identified in the reviewed sources.

Timeline

Published
2020-05-30explicit

Related visual models

Related cases

All 19 cases in Authorization and tenant boundaries

Sources

  1. Sign in with Apple failed to bind identity claims to the authenticated userBhavuk Jain · reviewed 2026-10-04
  2. iOS Security, iOS 12.3, May 2019, printed page 87: denomination context onlyApple · reviewed 2026-10-04

Record reviewed 2026-10-04. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software