[HN Gopher] Google Cloud SQL Incident
___________________________________________________________________
Google Cloud SQL Incident
Author : keltex
Score : 43 points
Date : 2021-01-29 20:32 UTC (2 hours ago)
(HTM) web link (status.cloud.google.com)
(TXT) w3m dump (status.cloud.google.com)
| markyc wrote:
| also discussed here:
| https://news.ycombinator.com/item?id=25960649
| nwsm wrote:
| Not seeing any issues in my side project's instance (us-
| central1-b).
| ashr wrote:
| Looks like something common between the control plane and data
| plane failed or there is a run-time dependency between the two
| (bad!) and that dependency failed.
| john37386 wrote:
| Can it be link to CVE-2021-3156 ?
|
| 10 years old sudo vulnerability.
| Kwpolska wrote:
| No, it can't. To exploit this vulnerability, you need the
| ability to run shell commands/arbitrary code on the system.
| Google Cloud SQL only lets you run SQL, and I would expect the
| servers to be locked down pretty heavily when it comes to non-
| database stuff.
| john37386 wrote:
| Thanks for the info. It must be a coincidence then. The
| timing looked like there was a possibility
| Kwpolska wrote:
| The vulnerability was announced on Tuesday. And
| vulnerabilities typically don't cause unplanned outages
| like this.
| js4ever wrote:
| Or maybe it can! Dropping a shell in Cloud SQL:
| https://news.ycombinator.com/item?id=24216009
| zachberger wrote:
| > Instance creation, operations, and queries in us-central1
| region may result in 502 (backend timeout) or 503 (service
| unavailable) errors.
___________________________________________________________________
(page generated 2021-01-29 23:01 UTC)