What the demonstration did
Replaying the Public DNS and Azure demonstration
- 1
Stale DNS alias
Reported July 30, 2018A Starbucks DNS record still pointed to a Traffic Manager profile that was no longer registered.
- 2
Branded proof page
Reported July 30, 2018The researcher demonstrated control of a proof page reached through the Starbucks subdomain.
Impact
The public report shows that the researcher could serve a proof page under a Starbucks subdomain after its Azure Traffic Manager profile was no longer registered. The report does not document customer traffic, credential collection or access to Starbucks’ Azure account.
Would the controls have stopped it?
Retire DNS aliases when the service they reference is retired
Track DNS records alongside the services they name and remove obsolete aliases before releasing those services. If Azure DNS hosts the zone, a resource-linked alias to a supported Traffic Manager profile stops resolving when that resource is deleted. The public report does not identify the DNS hosting provider or establish use of a resource-linked alias.
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.
Replaying the Public DNS and Azure demonstration
1 · Stale DNS alias
1 Not covered2 · Branded proof page
1 Not coveredKey facts
- Patrik Hudak submitted the report to Starbucks on July 30, 2018.
- The DNS alias still referenced an Azure Traffic Manager profile that was no longer registered.
- The researcher used a proof page to show control of the subdomain’s content.
- The report was made public on August 9 with a resolved status. Its public metadata does not date the resolution separately.
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.Starbucks public vulnerability report #388622HackerOne (report by Patrik Hudak to Starbucks) · Aug 9, 2018 · ResearchFirsthand account of the test environment, observations and disclosure.
- 2.Prevent dangling DNS entries and avoid subdomain takeoverMicrosoft · undated · Vendor reportProvider documentation for the scope and limits of Prevent dangling DNS entries and avoid subdomain takeover.
- 3.Alias records overviewMicrosoft · undated · Vendor reportProvider documentation for the scope and limits of Alias records overview.
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.