Skip to main content
Back
DemonstrationGoogle Cloud
2 min read

Google fixed misleading organization names in its Cloud Console

Environment
Google Cloud Resource Manager research environment
When
The researcher reported the issue on November 29, 2018.Disclosed Jan 30, 2019
Entry
A researcher-controlled organization could display another organization’s name.

Ezequiel Pereira demonstrated that a misleading organization name in Google Cloud Console could lead a user to create a project under an organization Pereira controlled. Google corrected how organization names could be changed and how the console selected the parent organization. Pereira did not report that a customer project or billing account was compromised.

What the demonstration did

Researcher
Ezequiel Pereira
Internet
Google Cloud
Organization

Research environment / Google Cloud Resource Manager research environment

  1. 1

    A display name could misidentify the organization

    November 2018

    Pereira changed the display name of his own test organization despite the field being documented as read-only. The resource’s owner did not change.

  2. 2

    The console could select the wrong parent

    Reported November 29, 2018

    For a consumer account that could see only the shared test organization, the console required an organization choice. Creating a project without an organization was still supported outside that interface. Google corrected the selection behavior.

Impact

Pereira found that a misleading organization name and the console’s parent selection could place new projects under a hierarchy he controlled. He did not report a customer project or billing account being compromised.

Would the controls have stopped it?

Verify the organization behind a project

Google corrected the reported behavior. Verify the organization ID and selected parent when provisioning a project, particularly where users can see multiple hierarchies.

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
Ezequiel Pereira
Internet
Google Cloud
Organization

Research environment / Google Cloud Resource Manager research environment

1 · A display name could misidentify the organization

1 Not covered

2 · The console could select the wrong parent

1 Not covered

Key facts

  • Pereira reported the issue on November 29, 2018.
  • The display name was documented as read-only when Pereira demonstrated it could change.
  • Google corrected both the ability to change the name and the console behavior that steered users toward the shared organization.
  • On January 29, 2019, Pereira received a $7,500 reward through Google’s vulnerability rewards program.

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.
    $7.5k Google Cloud Platform organization issueEzequiel Pereira · Jan 30, 2019 · ResearchFirst-hand report of organization naming, project placement, Google’s fix and reward.
  2. 2.
    REST resource: organizationsGoogle Cloud · undated · AdvisoryGoogle documents the server-assigned display name and the organization’s resource identifier.
  3. 3.
    Resource hierarchyGoogle Cloud · undated · AdvisoryAn organization is the top-level parent for resources in its hierarchy.

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