5 ms·
Google Cloud SQL Incident
- markyc 6y agoalso discussed here: https://news.ycombinator.com/item?id=25960649 https://news.ycombinator.com/item?id=25960649
- john37386 6y agoCan it be link to CVE-2021-3156 ? 10 years old sudo vulnerability.
- Kwpolska 6y agoNo, 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 6y agoThanks for the info. It must be a coincidence then. The timing looked like there was a possibility
- Kwpolska 6y agoThe vulnerability was announced on Tuesday. And vulnerabilities typically don’t cause unplanned outages like this.
- js4ever 6y agoOr maybe it can! Dropping a shell in Cloud SQL: https://news.ycombinator.com/item?id=24216009 https://news.ycombinator.com/item?id=24216009
- zachberger 6y ago> Instance creation, operations, and queries in us-central1 region may result in 502 (backend timeout) or 503 (service unavailable) errors.
- nwsm 6y agoNot seeing any issues in my side project's instance (us-central1-b).
- ashr 6y agoLooks 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.
- curiousDog 6y agohow did you conclude that? Also, why is it bad to have common runtime dependencies between two services? Unless you mean a shared service.
- tzury 6y agohttps://status.cloud.google.com/incident/cloud-sql/21002 https://status.cloud.google.com/incident/cloud-sql/21002