Skip to main content
Back
ExposureAWS
2 min read

An unclaimed S3 bucket exposed project files from multiple organizations

Owner
Organizations whose files were found in an unclaimed S3 bucket
When
Found December 20, 2019. Opening date unknown. – Feb 17, 2020Disclosed Aug 5, 2020
Entry
A publicly readable S3 bucket held project materials from several organizations. The researchers could not establish its owner.

vpnMentor identified several organizations in files held in one S3 bucket. It contacted InMotionNow as a possible owner and reported the finding to AWS. The bucket closed on February 17. The report did not establish that InMotionNow operated it.

What was exposed

Independent research
vpnMentor
Internet
Project storage
Project files

A public data exposure / Unclaimed project files

  1. 1

    An unclaimed project bucket is public

    By December 20, 2019

    vpnMentor found an open AWS S3 bucket. It suspected the project management company InMotionNow was associated with the files, but could not confirm ownership.

  2. 2

    Researchers examine files from several organizations

    December 2019–February 2020

    The bucket held more than 5.5 million files totaling over 343 GB. Among the material examined were mailing lists, donor records and marketing documents from multiple organizations.

  3. 3

    The bucket closes

    February 17, 2020

    After contacting InMotionNow and notifying AWS three times, the researchers recorded closure on February 17. They notified other organizations represented in the data on March 16.

Impact

More than 5.5 million files totaling over 343 GB were publicly accessible. vpnMentor found mailing lists, donor records and marketing materials from multiple organizations. Bucket ownership remained unconfirmed.

Could this have been prevented?

Restrict access to the bucket holding client materials

If client project files are only for approved participants, apply S3 Block Public Access to their bucket and authorize readers by project. Confirm who owns the bucket and who can change its access settings.

Incident control assessments

2
Prevented
0
Contained
1
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.

Independent research
vpnMentor
Internet
Project storage
Project files

A public data exposure / Unclaimed project files

1 · An unclaimed project bucket is public

1 Prevented

2 · Researchers examine files from several organizations

1 Prevented

3 · The bucket closes

1 Not covered

Key facts

  • vpnMentor discovered the open bucket on December 20, 2019, and notified InMotionNow as a possible owner on December 26.
  • The researchers counted over 5.5 million files and reported more than 343 GB. They did not inspect every file.
  • AWS was notified on December 29, January 7 and January 30. The researchers date the closure to February 17.
  • vpnMentor contacted other organizations represented in the data on March 16. InMotionNow did not respond to the researchers, leaving ownership unresolved.

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.
    Report: Cybersecurity Firm’s Data Exposed, Among OthersvpnMentor · Aug 5, 2020 · ResearchFirst-hand discovery, material inspected, attribution and disclosure chronology

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