assessment targeting the Vitess software database scaler. Funded by the CNCF / The Linux Foundation, this project was carried out by Cure53 in February 2019 and revealed only three miscellaneous findings. In terms also used for testing. Access to all relevant code and documentation was granted. While the first project meeting provided the basis for the audit, a more ad-hoc kick-off meeting ensured that no major hurdles constructs. These were marked whenever a potential capacity for leading to buffer corruption, information leakages and other similar flaws has been identified. The secondary phase (Phase 2) of the test

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Vitess becomes a CNCF project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Scalability local topology service, which is hosted in that cell. The topology service contains most of the information about the Vitess tablets in its cell. This enables a cell to be taken down and rebuilt as a unit to a tablet via a VTGate server. 12 Tablet Types See the user guide VTTablet Modes for more information. • master - A replica tablet that happens to currently be the MySQL master for its shard. • replica

Security Audit, 2023 Table of contents Table of contents 1 Executive summary 2 Notable findings 3 Project Summary 4 Audit Scope 4 Threat model formalisation 5 Fuzzing 14 Issues found 16 SLSA review work and results from the audit. The audit was funded by the CNCF who hosts Vitess as a graduated project. Results summarised 12 security issues found 2 CVEs assigned Formalisation of VTAdmins threat CVE-2023-29194 Moderate ADA-VIT-SA23-12 CVE-2023-29195 Moderate 3 Vitess Security Audit, 2023 Project Summary The auditors of Ada Logics were: Name Title Email Adam Korczynski Security Engineer, Ada

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Vitess becomes a CNCF project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Scalability local topology service, which is hosted in that cell. The topology service contains most of the information about the Vitess tablets in its cell. This enables a cell to be taken down and rebuilt as a unit routed to a tablet via a VTGate server. Tablet Types See the user guide VTTablet Modes for more information. • master - A replica tablet that happens to currently be the MySQL master for its shard. • replica

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Vitess becomes a CNCF project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Scalability local topology service, which is hosted in that cell. The topology service contains most of the information about the Vitess tablets in its cell. This enables a cell to be taken down and rebuilt as a unit to a tablet via a VTGate server. 10 Tablet Types See the user guide VTTablet Modes for more information. • master - A replica tablet that happens to currently be the MySQL master for its shard. • replica

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Vitess becomes a CNCF project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Scalability local topology service, which is hosted in that cell. The topology service contains most of the information about the Vitess tablets in its cell. This enables a cell to be taken down and rebuilt as a unit complicated query with a cross shard join might need to first fetch information from a tablet keeping vindex lookup tables. Then use this information to query two different shards for more data and subsequently

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Vitess becomes a CNCF project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Scalability local topology service, which is hosted in that cell. The topology service contains most of the information about the Vitess tablets in its cell. This enables a cell to be taken down and rebuilt as a unit complicated query with a cross shard join might need to first fetch information from a tablet keeping vindex lookup tables. Then use this information to query two different shards for more data and subsequently

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Vitess becomes a CNCF project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Scalability local topology service, which is hosted in that cell. The topology service contains most of the information about the Vitess tablets in its cell. This enables a cell to be taken down and rebuilt as a unit complicated query with a cross shard join might need to first fetch information from a tablet keeping vindex lookup tables. Then use this information to query two different shards for more data and subsequently

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Vitess becomes a CNCF project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 local topology service, which is hosted in that cell. The topology service contains most of the information about the Vitess tablets in its cell. This enables a cell to be taken down and rebuilt as a unit complicated query with a cross shard join might need to first fetch information from a tablet keeping vindex lookup tables. Then use this information to query two different shards for more data and subsequently

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Vitess becomes a CNCF project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Scalability local topology service, which is hosted in that cell. The topology service contains most of the information about the Vitess tablets in its cell. This enables a cell to be taken down and rebuilt as a unit complicated query with a cross shard join might need to first fetch information from a tablet keeping vindex lookup tables. Then use this information to query two different shards for more data and subsequently