Skip to main content
Back
ExposureAWS
7 min read

WWE fan records in public S3 buckets

Owner
World Wrestling Entertainment (WWE)
When
not stated; found open in July 2017 – Jul 4, 2017Disclosed Jul 6, 2017
Entry
Parts of two Amazon S3 buckets of WWE marketing data were set to public access, so anyone with an internet connection could view and download them with no password; which setting opened them, who set it and when are not stated.

About 12 percent of one Amazon S3 bucket of WWE marketing data and 12 to 15 percent of a second were set to public access, readable by anyone with no password, while many folders stayed protected; which setting opened them, who set it and when are not stated. The first held 3,065,805 fan records from 2014 and 2015 in plain text, with names, addresses and survey answers on age, race, education and children; a configuration file in it named the second, which held European customer data from 2016 and WWE social media metrics. Kromtech researchers found both, WWE was alerted on July 4, 2017, and both buckets were secured within a couple of hours, per the finders. WWE says no card or password data was included; how long the buckets were open and whether anyone besides the researchers read them are not stated.

What was exposed

External Parties
Kromtech researchers
Forbes
Internet
Fan Marketing Buckets · Amazon S3
Fan Records Bucket
3,065,805 Fan Records
Configuration File
European Data Bucket
European Customer Data

Replaying the WWE July 2017 exposure

  1. 1

    Configured: parts of two marketing buckets open to the internet

    Not stated; until the notice of July 4, 2017

    About 12 percent of the first bucket and 12 to 15 percent of the second are set to public access while many folders stay protected; which setting opened them, who set it and when are not stated.

  2. 2

    Reachable: 3 million fan records and European customer data

    Not stated; until the notice of July 4, 2017

    Anyone with an internet connection can download the public part of the first bucket, 3,065,805 fan records in plain text, and a configuration file in it names the second bucket, whose public part holds European customer data and social media metrics.

  3. 3

    Found and closed: secured within hours of the notice

    July 2017; WWE alerted on July 4, 2017

    Kromtech researchers find both buckets and read their public parts; WWE is alerted on July 4, and both buckets are secured within a couple of hours, per the finders; how, and by whom, is not stated.

Impact

3,065,805 fan records with names, addresses and survey answers on age, race, education and children, and European customer data from 2016, were readable with no password until both buckets were secured within a couple of hours of the July 4, 2017 notice, per the finders; how long they were open and whether anyone besides the researchers read them are not stated, and WWE says no card or password data was included.

Outcome

Where cloud-provider controls fit

Amazon S3 Block Public Access on the account, or set for every account by an organization policy, would have refused the ACL or bucket policy that opened part of each bucket: a public grant on one folder is refused like one on the whole bucket. Object Ownership would have closed the ACL path, if an ACL is what opened them, and a service control policy would have kept the write to approved administrators. While the grants stood, a resource control policy that refuses requests with no principal, or the IgnorePublicAcls and RestrictPublicBuckets settings of the same block, would have kept anonymous readers out of both buckets, whatever a configuration file named. Each of these dates from after this exposure. Azure and Google Cloud refuse the same opening with the anonymous-access setting and the public access prevention constraint, and Oracle Cloud refuses a public bucket with a Security Zone. Finding a public bucket and closing it stay your job: the provider's checks report a public bucket rather than refuse it.

Could this have been prevented?

In hindsight, not as a whole. 1 control would have refused a step outright, and 6 controls would have limited one. 2 steps have no cloud-provider control. The counts below are control assessments, not attack stages: several can address the same step. The same replay with the controls in place before the incident shows where each phase would have been refused or bounded.

1
Prevented
6
Contained
2
Not covered

How it could have been prevented

The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.

External Parties
Kromtech researchers
Forbes
Internet
Fan Marketing Buckets · Amazon S3
Fan Records Bucket
3,065,805 Fan Records
Configuration File
European Data Bucket
European Customer Data

Replaying the WWE July 2017 exposure

1 · Configured: parts of two marketing buckets open to the internet

1 Prevented2 Contained3 on other clouds

2 · Reachable: 3 million fan records and European customer data

4 Contained6 on other clouds

3 · Found and closed: secured within hours of the notice

2 Not covered

Key facts

  • About 12 percent of a first Amazon S3 bucket of WWE marketing data, several gigabytes, and 12 to 15 percent of a second were set to public access, per the finders; which setting opened them, who set it and when were not stated
  • The first bucket held 3,065,805 fan records from 2014 and 2015 in plain text, with names, email and physical addresses and survey answers on education, age, race and children's age and gender; Forbes counted more than 3 million users as of July 6, 2017
  • A configuration file in a public archive of the first bucket named the second, which held European customer data from 2016, WWE social media metrics by country and saved Twitter search results; the finders called the European data billing details of several hundred thousand customers, while the samples Forbes reviewed showed names, addresses and telephone numbers
  • Many folders of the first bucket stayed protected and no information on wrestlers or staff was accessible, per the researchers; WWE said no payment card or password data was included
  • WWE was alerted on July 4, 2017, by the researcher per Forbes or by a Forbes reporter per Threatpost; the finders said both buckets were secured within a couple of hours of their email to WWE developers
  • How long the buckets were open and whether anyone besides the researchers read them were not stated; SecurityWeek saw no indication either way, and The Register said it was unclear whether WWE or a third-party developer operated the database

Sources

Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.

  1. 1.
    22 Data Breaches We Found and Reported in 2017 (section: World Wrestling Entertainment leaks 3 million emails)MacKeeper (Kromtech research) · Feb 19, 2026 · Researchtwo public S3 buckets, partial public access, record count and data types, second bucket found through a configuration file, European billing data, social media metrics, notification and closure within hours, no WWE answer on exposure length or access
  2. 2.
    WWE issues statement on cybersecurityWWE · Jul 6, 2017 · Vendor reportdatabase on AWS, secured, no card or password data, Smartronix and Praetorian, work with AWS
  3. 3.
    Massive WWE Leak Exposes 3 Million Wrestling Fans' Addresses, Ethnicities And MoreForbes (reposted on the BreachExchange list, seclists.org) · Jul 6, 2017 · Newsresearcher and firm, no username or password, plaintext, fields, European database contents, alert on July 4, WWE statement to Forbes, suspected misconfiguration
  4. 4.
    Unprotected server leaves 3 million WWE fans' personal data vulnerable: reportCNBC · Jul 6, 2017 · NewsWWE statement as given to the press, access with no username or password, second database
  5. 5.
    Leaky WWE Database Exposes Personal Data of 3M Wrestling FansThreatpost · Jul 7, 2017 · Newswho alerted WWE, unknown other access, misconfiguration by WWE or an IT provider
  6. 6.
    Bah Gawd! WWE left wrasslin' fans' privates on display onlineThe Register · Jul 7, 2017 · NewsWWE statement, unclear operator of the database, European store customers
  7. 7.
    WWE Exposes Details of 3 Million Customers on AWSSecurityWeek · Jul 7, 2017 · Newsat least two databases, no indication of other access, July 4 report to WWE

The estate in the replay is illustrative and drawn at the level of the exposure; the owner's real environment is not public. Verdicts describe what a control does when it is in place before the data is exposed. They are not an assessment of the owner's security program.

More cloud attack breakdowns

All breakdowns