Skip to main content
Back
ExposureAWS
10 min read

Cultura Colectiva and At the Pool public S3 buckets

Owner
Cultura Colectiva and At the Pool
When
Jan 10, 2019 – Apr 3, 2019Disclosed Apr 3, 2019
Entry
Two Amazon S3 buckets configured to allow public download of their files, Cultura Colectiva's cc-datalake and a bucket whose name is not stated with a database backup of the At the Pool app; which setting opened them, an ACL or a bucket policy, who set it and when are not stated.

UpGuard found two Amazon S3 buckets configured to allow public download: Cultura Colectiva's cc-datalake, with 146 GB and over 540 million records of comments, likes, reactions, account names and Facebook IDs, and a bucket with a database backup of At the Pool, an app that ceased operation in 2014, with plaintext passwords for 22,000 users. UpGuard emailed Cultura Colectiva on January 10 and 14, 2019 and notified AWS on January 28 and February 21; cc-datalake stayed open until the morning of April 3, after Bloomberg asked Facebook for comment and Facebook contacted Amazon, and the At the Pool backup went offline earlier, before a formal notice, for a reason no source gives. Whether anyone other than UpGuard read either dataset is not stated, and Facebook said it had no evidence yet of misuse.

What was exposed

External Parties
UpGuard
Facebook
Internet
At the Pool Backup · Amazon S3
Cultura Colectiva Data Lake · Amazon S3
Backup Bucket · public
Plaintext Passwords
cc-datalake Bucket · public
Records · 540M+

Replaying the Cultura Colectiva January 2019 exposure

  1. 1

    Configured: two buckets open to public download

    Dates not stated; cc-datalake open by Jan 10, 2019

    Two Amazon S3 buckets, Cultura Colectiva's cc-datalake and one with a backup of the At the Pool app, allow public download of their files; which setting opened them, who set it and when are not stated.

  2. 2

    Reachable: 146 GB of records and 22,000 passwords

    cc-datalake at least Jan 10–Apr 3, 2019

    Anyone on the internet can download cc-datalake's 146 GB and over 540 million records for at least 83 days, and the At the Pool backup with plaintext passwords for 22,000 users for an unknown period; whether anyone other than UpGuard read either is not stated.

  3. 3

    Found and closed: 83 days after the first notice

    Jan 10–Apr 3, 2019

    UpGuard's emails to Cultura Colectiva go unanswered and AWS replies that the owner was told; the At the Pool backup goes offline before a formal notice, for a reason no source gives, and cc-datalake is secured on April 3 after Bloomberg asks Facebook for comment and Facebook contacts Amazon.

Impact

146 GB and over 540 million records of comments, likes, reactions, account names and Facebook IDs in cc-datalake, and names, email addresses, Facebook IDs, profile columns and plaintext passwords for 22,000 users in the At the Pool backup, downloadable by anyone on the internet; cc-datalake stood open at least 83 days until it was secured on April 3, 2019, and whether anyone other than the finder read either dataset is not stated.

Outcome

Where cloud-provider controls fit

Amazon S3 Block Public Access on each account, kept on by a service control policy, would have refused the ACL or bucket policy that opened either bucket. Object Ownership closes the ACL path only, and no source says which setting opened them. Azure, Google Cloud and Oracle Cloud refuse the same opening with the anonymous-access setting, the public access prevention constraint and a Security Zone. Once a grant stood, the account-level block or a resource control policy would have refused anonymous and off-network reads without anyone touching the bucket, which matters for a backup nobody may have been looking after; on Azure and Google Cloud the same setting and constraint refuse the read. The unanswered emails, the backup's unexplained closing and the takedown after a newsroom's call stay outside the provider's controls: closing a public bucket is your change to make, and the provider's checks report one rather than refuse it.

Could this have been prevented?

In hindsight, not as a whole. 2 controls would have refused a step outright, and 9 controls would have limited one. 3 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.

2
Prevented
9
Contained
3
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
UpGuard
Facebook
Internet
At the Pool Backup · Amazon S3
Cultura Colectiva Data Lake · Amazon S3
Backup Bucket · public
Plaintext Passwords
cc-datalake Bucket · public
Records · 540M+

Replaying the Cultura Colectiva January 2019 exposure

1 · Configured: two buckets open to public download

2 Prevented3 Contained8 on other clouds

2 · Reachable: 146 GB of records and 22,000 passwords

6 Contained6 on other clouds

3 · Found and closed: 83 days after the first notice

3 Not covered

Key facts

  • cc-datalake held 146 GB and over 540 million records of comments, likes, reactions, account names and Facebook IDs; the figure counts records, not users, and the number of unique users was not stated
  • The At the Pool backup held names, email addresses, Facebook IDs, friends, likes, check-ins and other profile columns, and plaintext passwords for 22,000 users, which UpGuard presumed were app passwords rather than Facebook passwords
  • UpGuard emailed Cultura Colectiva on January 10 and 14, 2019 and had no response; it notified AWS on January 28, and AWS replied on February 1 that the owner had been made aware, while Bloomberg dated Amazon's first response to February 21
  • cc-datalake was secured on the morning of April 3, 2019, at least 83 days after the first notice, after Bloomberg asked Facebook for comment and Facebook contacted Amazon; who secured it and how were not stated
  • The At the Pool backup went offline while UpGuard was tracing its origin, before a formal notice; who or what took it offline and how long it had been exposed were not stated
  • Facebook said it had no evidence yet of misuse, Cultura Colectiva said the data came from its three Facebook pages and its users' privacy was not at risk, and Mexico's data protection authority INAI opened an ex officio investigation whose outcome was not reported

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.
    Losing Face: Two More Cases of Third-Party Facebook App Data ExposureUpGuard · Apr 3, 2019 · ResearchDatasets, bucket name, sizes, counts, data fields, notification timeline, AWS replies, securing date, At the Pool takedown
  2. 2.
    Millions of Facebook records found on Amazon cloud serversBloomberg, syndicated by TechCentral · Apr 3, 2019 · NewsFacebook statement, Bloomberg alert, takedown, AWS no comment, At the Pool window, unique-user count unknown
  3. 3.
    Amazon Cloud Storage Dilemma Exposed in Facebook's Latest LeakBloomberg, republished by Data Center Knowledge · Apr 4, 2019 · NewsAWS statements, AWS reply dates, who removed the data, researcher's account
  4. 4.
    UPDATE 2-Facebook removes exposed user records stored on Amazon's serversReuters, via CNBC · Apr 3, 2019 · NewsFacebook statement, Cultura Colectiva statement, Amazon no reply, At the Pool counts
  5. 5.
    Researchers find 540 million Facebook user records on exposed serversTechCrunch · Apr 3, 2019 · NewsFacebook statement, misuse statement, Amazon takedown request, At the Pool fields
  6. 6.
    Datos de millones de usuarios de Facebook fueron expuestos en una nube de AmazonExpansión · Apr 3, 2019 · NewsCultura Colectiva statement (Spanish), Facebook statement (Spanish), tweet
  7. 7.
    App Developers Exposed 540 Million Facebook User Records on Public InternetVICE (Motherboard) · Apr 3, 2019 · NewsCultura Colectiva emailed statement, records versus users, data origin
  8. 8.
    El INAI investiga posible uso irregular de datos por parte de Cultura ColectivaExpansión Política (ADNPolítico) · Apr 3, 2019 · NewsR3D request, INAI tweet, Cultura Colectiva statement, database closed
  9. 9.
    Inicia INAI investigación de oficio contra Cultura ColectivaExpansión · Apr 6, 2019 · NewsINAI investigation, legal basis

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