. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 I cannot start a cluster, and see these errors in the logs: Could not open required defaults file: /path/to/my.cnf . 40 Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 4 Problems with DROP TABLE 70 Vitess table lifecycle 70 Lifecycle subsets and configuration 71 Automated lifecycle 71 User-facing DROP TABLE lifecycle 71 Tablet throttler . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 I cannot start a cluster, and see these errors in the logs: Could not open required defaults file: /path/to/my.cnf . 27 Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 File:Position based VReplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 VTTablet YAML configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 File:Position based VReplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 VTTablet YAML configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Lifecycle subsets and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Stateless

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 File:Position based VReplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 VTTablet YAML configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Lifecycle subsets and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Stateless

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 File:Position based VReplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 VTTablet YAML configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Lifecycle subsets and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Stateless

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 I cannot start a cluster, and see these errors in the logs: Could not open required defaults file: /path/to/my.cnf . 26 Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 I cannot start a cluster, and see these errors in the logs: Could not open required defaults file: /path/to/my.cnf . 23 Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Orchestrator configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 VTTablet configuration . . . . . . . . . . . . . . .

being only an administrative functionality, a typical example for such functions interacting with the file system would be ExecuteHook. This item was analyzed in depth to see if it is by any means possible as with most information leak issues in general, would need to be considered as low. • The configuration of the Kubernetes cluster deployment was investigated for common problems like AllowPrivilegeEscalation traversal and OS-level command injection were attempted for every function that interacted with the file system. Cure53, Berlin · 03/08/19 4/9 Dr.-Ing. Mario Heiderich

with local network or local file access An actor that has breached some security boundaries of the environment to get to the position of having access to the local network or file system. Yes Well-funded that an attacker can compromise, 1) the file system of a running VTAdmin deployment, and 2) an app that is responsible for authenticating the VTAdmin-web client. File system Trust increases when an actor actor obtains access to the local file system. An attacker with local access may be able to access VTAdmin-web. In this case, the trust boundary is the local file system. 10 Vitess Security Audit, 2023