2018 · United States · J - Information and communication · Account takeover via stolen access tokens (platform code vulnerability)
Analysed 2026-11-07 by Hermes
Open this case in the tool →Account takeover via stolen access tokens (platform code vulnerability)
Strategy to Execution
Evidence coverage: 2/6 stages, weight 15/60
Decisive stage: entry (clearest evidence) · Alternative: Expertise to Execution
(1) Facebook ran View As as a privacy feature that was supposed to be a view-only interface, and its EU controller MPIL operated under data-protection-by-design and by-default obligations (GDPR Articles 25(1)/(2), in force since May 2018) that required tokens and interfaces to grant only the access a purpose needs. (2) In practice, a July 2017 video-upload change interacted with the Happy Birthday Composer inside View As so that the platform generated a fully permissioned access token for the profile being viewed and exposed it in the page HTML; the three-bug interaction sat unnoticed in production until unauthorised persons exploited it with scripts between 14 and 28 September 2018, taking over approximately 29 million accounts (~3 million EU/EEA); own monitoring flagged anomalous video-upload activity, the flaw was fixed and ~90 million tokens were reset, and the incident was self-disclosed on 28 September 2018. (3) The classification rests on the entry (pre-breach design) stage, where the evidence is clearest and load-bearing: the Irish DPC's final decision (December 2024) documents that by-design and by-default obligations existed (doctrinal origin) yet MPIL failed to implement appropriate technical and organisational measures, failed to use alternative, more appropriate measures, and deployed tokens with unnecessarily broad access - the obligation never materialised in the architecture (execution break); no source shows leadership deferring or discounting it. The response stage shows the same doctrinal-to-execution pattern (notification duty documented, notification incomplete and undocumented, per Article 33 findings) and is contributing, not decisive; detection, containment and recovery are documented as working, and the actor is unattributed and not load-bearing. RM29 (Strategy to Execution lens): application-security requirements were not implemented in practice - View As shipped and ran for over a year with code contradicting its own view-only design, and the regulator found secure-by-design measures were never applied to token generation (causal role: Enabling). RM20 (Strategy to Execution lens): the July 2017 change to the video uploader altered the security posture of a privacy feature, and the validation and testing that would have caught the three-bug interaction never materialised in the change process (causal role: Enabling). RM22 (Strategy to Execution lens): account-lifecycle and token-scoping rules that should have confined a session token to the session user were not enforced in configuration - the platform generated fully permissioned tokens for another user's profile and leaked them in HTML, letting attackers log in as legitimate users at scale (causal role: Enabling). RM39 (Strategy to Execution lens): notification obligations existed and notification was in fact filed on 28 September 2018, but the workflow was not operationalised to the required standard - the DPC found it omitted information MPIL could and should have included and no contemporaneous record was kept (causal role: Constraining).
RM29 — Secure-development / non-production exposureRM20 — Change / transition control failureRM22 — Authentication / credential exposureRM39 — Breach notification / disclosure failureEuRepoC row for the September 2018 Facebook View As hack; description (50 million users, three weaknesses) matches the victim's initial disclosure and Facebook's own statement of three distinct bugs; the figure was revised to ~30 million (Facebook, Oct 2018) and ~29 million (DPC decision) - the row carries the initial-disclosure number. The regulator decision (Irish DPC, adopted 12 December 2024, announced 17 December 2024) is addressed to Meta Platforms Ireland Limited (EU controller for Facebook); the victim is recorded as Facebook, country from eurepoc_extra.receiver_country (US, HQ). Actor unattributed in the dataset and left unattributed; attribution is not load-bearing for the DV. Source caveat: the dataset's first source_url (nytimes.com article on the hack) could not be opened (HTTP error) and is not cited; it is replaced by the victim's own disclosure and the DPC decision and press release, all opened during this analysis. DPC findings relied on: Article 25(1)/25(2) (fines EUR 130m + 110m, by-design/by-default) for the entry gap and Article 33(3)/33(5) (fines EUR 8m + 3m, notification content and record) for the response gap.