Skip to main content
Back
DemonstrationAWS
1 min read

Public S3 permissions put website assets at risk

Environment
Website and asset owners studied by Detectify
When
Research published July 13, 2017Disclosed Jul 13, 2017
Entry
Detectify identified public S3 grants that let outsiders change website assets or their permissions.

Detectify identified public S3 grants that let outsiders change website assets or their permissions. Detectify found vulnerable third-party assets on login pages. It reported the findings to the affected parties.

What the demonstration did

Researcher
Detectify
Internet
S3 bucket
Website assets

S3 bucket / Detectify research

  1. 1

    Public grants put assets at risk

    Reported July 13, 2017

    Detectify identified public S3 grants that let outsiders change website assets or their permissions.

  2. 2

    Websites depend on third-party assets

    Reported July 13, 2017

    Detectify found vulnerable third-party assets on login pages. It reported the findings to the affected parties.

Impact

Detectify found website assets whose contents or permissions outsiders could change. Some appeared on company login pages. The report gives no count of compromised visitors.

Would the controls have stopped it?

Ignore public write grants on website assets

If public reads can use a bucket policy, enable IgnorePublicAcls on the asset bucket to neutralize public ACL grants. Review the bucket policy separately. AWS introduced this setting after the research.

Incident control assessments

1
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.

Researcher
Detectify
Internet
S3 bucket
Website assets

S3 bucket / Detectify research

1 · Public grants put assets at risk

1 Prevented

2 · Websites depend on third-party assets

1 Not covered

Key facts

  • Detectify examined permissions on both S3 buckets and individual objects.
  • Researchers identified vulnerable assets on company login pages.
  • Some sites loaded third-party assets through Google Tag Manager.
  • Detectify contacted affected parties, and reported that some providers corrected the issue quickly.

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.
    A deep dive into AWS S3 access controls: taking full control over your assetsDetectify · Jul 13, 2017 · ResearchFirst-hand account of the finding, its scope and the response.
  2. 2.
    Blocking public access to your Amazon S3 storageAWS · undated · Vendor reportHow IgnorePublicAcls treats existing public group grants.
  3. 3.
    Introducing Amazon S3 Block Public AccessAWS · Nov 15, 2018 · Vendor reportRelease after the 2017 research.

The estate in the replay follows the researchers' description of their own test environment. Verdicts describe what a control does when it is in place before the run. They are not an assessment of any company's security program.

More cloud attack breakdowns

All breakdowns