The classifier judged this item not relevant to AI security, so it is left out of lists, feeds, the API and dataset releases. If that is wrong, report a correction on this page.
GCP Apigee Space and Environment Isolation Bypass Using Internal Services
- Published
- Record updated
Summary
Tenable Research disclosed an authorization bypass in Google Cloud Apigee that lets an attacker with apigee.deployments.create permission in one environment exfiltrate runtime contracts, including proxy source code, policies and configurations, from other environments or Spaces on the same instance. The attacker deploys a custom API proxy that queries the unauthenticated internal Prometheus endpoint apigee-metrics-default-telemetry-app.apigee.svc.cluster.local:9090 to find synchronizer pod IPs, then requests the runtime contract ZIP from the synchronizer on port 8843.
Mitigation
The source does not state a fix yet. Check the original advisory for updates.