Synopsis
Tenable Research discovered a privilege escalation vulnerability in Google Cloud Platform (GCP) that is now fixed. The vulnerability could have allowed an identity with edit permissions on a Google Cloud Run revision to abuse those to pull private Google Artifact Registry and Google Container Registry images in the same account without any registry permissions.
Solution
In response to this discovery, GCP now makes sure that the principal (user or service account) creating or updating a Cloud Run resource now needs explicit permission to access the container image(s). When using Artifact Registry, ensure the principal has the Artifact Registry Reader (roles/artifactregistry.reader) IAM role on the project or repository containing the container image(s) to deploy.
The breaking change was 100% rolled out to production on 28 January 2025. A Mandatory Service Announcement was sent to affected Project, Folder, and Organization owners during the last week of November 2024 and the Release Notes warned users of the breaking change coming in January 2025.
After this fix Cloud Run checks to confirm that the deployer has read access to the image.
Disclosure Timeline
All information within TRA advisories is provided “as is”, without warranty of any kind, including the implied warranties of merchantability and fitness for a particular purpose, and with no guarantee of completeness, accuracy, or timeliness. Individuals and organizations are responsible for assessing the impact of any actual or potential security vulnerability.
Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.
For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.
If you have questions or corrections about this advisory, please email [email protected]