Skip to main content
Back
DemonstrationAWS
1 min read

An AWS CloudTrail export carries active spreadsheet content into a test workstation

Environment
Rhino Security Labs’ AWS account and test workstation
When
Reported to AWS December 13, 2017Disclosed Feb 6, 2018
Entry
CloudTrail recorded user-influenced content from a rejected operation in the research account.

Rhino Security Labs showed that an AWS CloudTrail export could carry a spreadsheet formula entered as part of a rejected request. In the researchers’ test, the spreadsheet ran the formula after a user confirmed a prompt. The effect was on the analyst’s workstation. AWS still denied the original request.

What the demonstration did

Research team
Rhino Security Labs
Internet
AWS audit review
Audit export

Replaying the AWS audit review demonstration

  1. 1

    Rejected request logged

    Reported to AWS December 13, 2017

    CloudTrail recorded user-influenced content from a rejected operation in the research account.

  2. 2

    Analyst workstation

    Reported to AWS December 13, 2017

    The researchers observed an affected spreadsheet evaluate content from the event export after user confirmation.

Impact

In its own AWS account, Rhino Security Labs confirmed that a rejected request left content in an audit export. An affected spreadsheet evaluated that content on the test workstation after user confirmation. CloudTrail did not grant the rejected permission.

Would the controls have stopped it?

Keep exported audit evidence inert on the analyst’s workstation

Preserve the original event record and use a viewer that treats its fields as data. Where evidence must be opened in a spreadsheet, control how the client imports untrusted text and restrict its ability to launch external applications. AWS authorization of the original request acts at a different boundary.

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.

Research team
Rhino Security Labs
Internet
AWS audit review
Audit export

Replaying the AWS audit review demonstration

1 · Rejected request logged

1 Not covered

2 · Analyst workstation

1 Not covered

Key facts

  • Rhino Security Labs used a test AWS account and a workstation under its control.
  • CloudTrail recorded information from a rejected operation.
  • The researchers observed spreadsheet evaluation after user interaction with a downloaded CSV export.
  • AWS discussed its response on January 12, 2018, and opted to document the risk for users.

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.
    Cloud Security Risks (P2): CSV Injection in AWS CloudTrailRhino Security Labs · Feb 6, 2018 · ResearchFirsthand account of the test environment, observations and disclosure.
  2. 2.
    Working with CloudTrail event historyAWS · undated · Vendor reportProvider documentation for the scope and limits of Working with CloudTrail event history.

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