. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 File:Position based VReplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 Format of the table ACL config file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390 5. Add your SQL schema to the output file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 6. Add your VSchema

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 File:Position based VReplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Format of the table ACL config file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 5. Add your SQL schema to the output file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 6. Add your VSchema

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 File:Position based VReplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 Format of the table ACL config file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427 5. Add your SQL schema to the output file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427 6. Add your VSchema

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 File:Position based VReplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 Format of the table ACL config file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506 5. Add your SQL schema to the output file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506 6. Add your VSchema

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . that Vitess will require. It is recommended to put these in your .bashrc: # Additions to ~/.bashrc file # Add go PATH export PATH=$PATH:/usr/local/go/bin # Vitess binaries export PATH=~/vitess/bin:${PATH} failed: /usr/sbin/mysqld: exit status 1, output: mysqld: [ERROR] Failed to open required defaults file: /home/morgo/vitess/vtdataroot/vt_0000000102/my.cnf mysqld: [ERROR] Fatal error in defaults handling

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Format of the table ACL config file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 5. Add your SQL schema to the output file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 6. Add your VSchema

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . that Vitess will require. It is recommended to put these in your .bashrc: # Additions to ~/.bashrc file # Add go PATH export PATH=$PATH:/usr/local/go/bin # Vitess binaries export PATH=~/vitess/bin:${PATH} failed: /usr/sbin/mysqld: exit status 1, output: mysqld: [ERROR] Failed to open required defaults file: /home/morgo/vitess/vtdataroot/vt_0000000102/my.cnf mysqld: [ERROR] Fatal error in defaults handling

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . that Vitess will require. It is recommended to put these in your .bashrc: # Additions to ~/.bashrc file # Add go PATH export PATH=$PATH:/usr/local/go/bin # Vitess binaries export PATH=~/vitess/bin:${PATH} failed: /usr/sbin/mysqld: exit status 1, output: mysqld: [ERROR] Failed to open required defaults file: /home/morgo/vitess/vtdataroot/vt_0000000102/my.cnf mysqld: [ERROR] Fatal error in defaults handling

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

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 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 attempt to execute commands as root. The unachieved goal was to have file system-level capabilities and turn them into direct file manipulation. • After checking all user-exposed endpoints, the application-level