Skip to main content
Back
DemonstrationAzure
1 min read

An Azure Activity Log export crosses a spreadsheet trust boundary

Environment
Rhino Security Labs’ Azure subscription and test workstation
When
Reported to Microsoft December 21, 2017Disclosed Jan 24, 2018
Entry
A rejected operation left user-influenced text in the Azure Activity Log.

Rhino Security Labs showed that a rejected Azure request could leave content in an Activity Log export that a spreadsheet would run. This happened on the researchers’ test workstation after they opened the export and accepted a warning. The test did not increase their Azure permissions.

What the demonstration did

Research team
Rhino Security Labs
Internet
Azure audit review
Activity Log export

Replaying the Azure audit review demonstration

  1. 1

    Activity Log record

    Reported to Microsoft December 21, 2017

    A rejected operation left user-influenced text in the Azure Activity Log.

  2. 2

    Spreadsheet evaluation

    Reported to Microsoft December 21, 2017

    The researchers observed active content evaluated on their test workstation after opening the export and confirming a warning.

Impact

The test subscription retained details of a rejected resource operation. When the researchers opened the exported data in an affected spreadsheet and approved its warning, the content ran on the test workstation. The test did not elevate Azure permissions.

Would the controls have stopped it?

Read Azure Activity Log fields as untrusted text

Azure should retain evidence of rejected activity. Inspect the record in a viewer that treats fields as text, and control the handling of spreadsheet imports on analyst workstations. Microsoft’s download-format change reduced accidental spreadsheet opening. A filename change alone cannot make active text safe in every client.

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
Azure audit review
Activity Log export

Replaying the Azure audit review demonstration

1 · Activity Log record

1 Not covered

2 · Spreadsheet evaluation

1 Not covered

Key facts

  • Rhino Security Labs observed user-influenced text in the Activity Log of its test subscription.
  • The underlying Azure resource operation was rejected.
  • The desktop result required opening the export in a spreadsheet and interacting with a warning.
  • On January 15, 2018, the researchers found that Azure added a text-file extension to the download.

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 (Part 1): Azure CSV Injection VulnerabilityRhino Security Labs · Jan 24, 2018 · ResearchFirsthand account of the test environment, observations and disclosure.
  2. 2.
    Activity Log in Azure MonitorMicrosoft · undated · Vendor reportProvider documentation for the scope and limits of Activity Log in Azure Monitor.

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