Skip to main content
Back
DemonstrationAWS
1 min read

Yahoo’s Luminate screenshot service exposes an EC2 role credential

Environment
Yahoo’s bug-bounty test of Luminate
When
Jun 12, 2017Disclosed Jun 23, 2017
Entry
The screenshot application made requests outside the destinations intended for its users.

The screenshot application made requests outside the destinations intended for its users. The research report documents an EC2 instance-role credential returned through the application.

What the demonstration did

Research team
DOS researchers
Internet
Luminate on EC2
Screenshot service

Replaying the Luminate on EC2 demonstration

  1. 1

    Application requests

    Testing began June 12, 2017

    The screenshot application made requests outside the destinations intended for its users.

  2. 2

    Instance metadata

    Testing began June 12, 2017

    The research report documents an EC2 instance-role credential returned through the application.

Impact

The researchers saw temporary credentials associated with the service’s EC2 instance role and stopped testing. They did not report using the credentials to access customer data or other AWS resources.

Would the controls have stopped it?

Require session tokens for EC2 instance metadata

An EC2 instance that requires IMDSv2 refuses a metadata read without a session token. This later AWS feature addresses the request the researchers demonstrated. The application still needs to restrict its outbound destinations, and the attached role should have only the access it requires.

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.

Research team
DOS researchers
Internet
Luminate on EC2
Screenshot service

Replaying the Luminate on EC2 demonstration

1 · Application requests

1 Not covered

2 · Instance metadata

1 Prevented

Key facts

  • The researchers identified the screenshot service on June 12, 2017.
  • They confirmed the credential exposure and reported it to Yahoo on June 13.
  • They stopped testing after observing the role credentials.
  • Yahoo took the endpoint offline and rotated the keys on June 13, according to the researchers.

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.
    Yahoo Small Business (Luminate) and the Not-So-Secret Keysdos.sh (the researchers) · Jun 23, 2017 · ResearchFirsthand account of the test environment, observations and disclosure.
  2. 2.
    Configure the Instance Metadata Service optionsAWS · undated · Vendor reportProvider documentation for the scope and limits of Configure the Instance Metadata Service options.
  3. 3.
    Add defense in depth against open firewalls, reverse proxies, and SSRF vulnerabilities with enhancements to the EC2 Instance Metadata ServiceAWS · undated · Vendor reportProvider documentation for the scope and limits of Add defense in depth against open firewalls, reverse proxies, and SSRF vulnerabilities with enhancements to the EC2 Instance Metadata Service.

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