Skip to main content
Back
DemonstrationGoogle Cloud · Kubernetes
1 min read

Shopify isolated a metadata exposure in Exchange

Environment
Shopify Exchange
When
Apr 22, 2018Disclosed May 23, 2018
Entry
A researcher reported that Exchange’s screenshot service could reach internal metadata. Shopify placed the affected containers in one infrastructure subset.

A researcher found a flaw in the screenshot service for Shopify Exchange. Shopify confirmed that it could give a researcher full control of containers in one part of its infrastructure. That area excluded Shopify’s core platform, although some applications there could reach core systems or data. Shopify disabled the screenshot service within an hour.

What the demonstration did

Researcher
0xacb
Internet
Service subset
Exchange service

Service subset / 0xacb research

  1. 1

    The screenshot service reached internal resources

    April 22, 2018

    A researcher reported that Exchange’s screenshot service could reach internal metadata. Shopify placed the affected containers in one infrastructure subset.

  2. 2

    Shopify disabled the service and changed its network access

    After notification

    Shopify disabled the vulnerable service within an hour, audited its services, and deployed a proxy that concealed metadata.

Impact

Shopify confirmed that the issue could give a researcher root access to containers in one infrastructure subset. That subset excluded Shopify core, although some applications there could access core data or systems.

Would the controls have stopped it?

Isolate screenshot workers from internal metadata

Shopify used a metadata concealment proxy and blocked access to internal addresses. On Kubernetes, egress policies can restrict other destinations, but node-local traffic needs separate protection.

Incident control assessments

0
Prevented
0
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.

Researcher
0xacb
Internet
Service subset
Exchange service

Service subset / 0xacb research

1 · The screenshot service reached internal resources

1 Not covered

2 · Shopify disabled the service and changed its network access

1 Not covered

Key facts

  • The researcher reported the issue to Shopify on April 22, 2018.
  • Shopify disabled the affected service within an hour of receiving the report.
  • Shopify reviewed services across its infrastructure subsets.
  • Shopify awarded $25,000 and publicly disclosed the report on May 23, 2018.

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.
    SSRF in Exchange leads to ROOT access in all instancesShopify and 0xacb on HackerOne · May 23, 2018 · ResearchFirst-hand account of the finding, its scope and the response.
  2. 2.
    Network PoliciesKubernetes · undated · Vendor reportEgress isolation, plugin enforcement and node traffic exceptions.

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