Skip to main content
Back
ExposureAWS
2 min read

VEED user videos were public in Amazon S3

Owner
VEED
When
Found October 12, 2019. Opening date unknown.Disclosed Nov 20, 2019
Entry
VEED user uploads were accessible in an unsecured S3 bucket.

vpnMentor found an open bucket behind the VEED editor in October 2019. It notified VEED and then AWS. The public access closed after AWS contacted VEED. The report did not establish whether anyone else downloaded the videos.

What was exposed

Independent research
vpnMentor
Internet
Video storage
User videos

A public data exposure / VEED video storage

  1. 1

    The video bucket is open to the public

    By October 12, 2019

    An Amazon S3 bucket for VEED’s video editor allowed public access. The exact public grant was not identified.

  2. 2

    Researchers examine uploaded videos

    October 2019

    vpnMentor found tens of thousands of raw and edited videos, including marketing work and private family material. It could not determine which uploads users meant to publish.

  3. 3

    The video bucket closes

    After AWS contacted VEED

    The researchers notified VEED on October 15 and AWS on October 27. They report closure after AWS contacted VEED and list an action around November 5. They do not give a separate date for closure.

Impact

Tens of thousands of raw and edited VEED videos were publicly accessible. The researchers saw private family material alongside videos made for marketing.

Could this have been prevented?

Keep private video uploads separate from published copies

If private originals are kept in their own S3 bucket, enable S3 Block Public Access on that bucket. Serve videos their creators choose to publish through a separate delivery path.

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
Video storage
User videos

A public data exposure / VEED video storage

1 · The video bucket is open to the public

1 Prevented

2 · Researchers examine uploaded videos

1 Prevented

3 · The video bucket closes

1 Not covered

Key facts

  • vpnMentor found the open bucket on October 12 and contacted VEED on October 15.
  • The researchers could read both raw uploads and edited versions. They could not determine which videos users intended to publish.
  • AWS received the report on October 27 and replied on October 29. vpnMentor dates the action to approximately November 5.
  • The report is dated November 20. Its updated timeline records a VEED reply on November 21.

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: VEED.io Exposes Private User Videos in Data LeakvpnMentor · Nov 20, 2019 · 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