Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 36 additions & 0 deletions content/en/blog/2023-05-31-vitess-security-audit.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
---
author: 'Deepthi Sigireddi'
date: 2023-05-31
slug: '2023-05-31-vitess-security-audit'
tags: ['security','Vitess','MySQL']
title: 'Vitess Security Audit Results'
description: "Third-party security audit of Vitess completed"
---

The Vitess Maintainer team is pleased to announce the results of a recent third-party security audit of the Vitess code base.

Vitess had previously been audited in 2019. Given the amount of time that has passed, and the magnitude of change during that time, the maintainer team decided to request a fresh audit.
Starting in March 2023, an independent team from AdaLogics performed a full security audit of Vitess with special emphasis on VTAdmin, which is a relatively new addition to Vitess.
Comment thread
deepthi marked this conversation as resolved.
Outdated

## Scope
The goals of the audit were to:

* Produce a formal threat model of VTAdmin.
* Perform a manual audit of the VTAdmin code following the threat model.
* Align Vitess’s fuzzing suite with the threats identified by the maintainers.
* Perform a manual audit of the remaining Vitess code base.
* Conduct a Supply Chain Levels for Software Artifacts (SLSA) review of Vitess.

## Outcomes
* No Critical issues were found during the audit.
* A number of Moderate/Low/Informational issues were reported.
* The project published 2 Moderate Severity CVEs and patch releases with associated fixes for them.
* All the reported issues that are under our control have either been fixed, or have a plan in place to be fixed before the end of the year.
* We ended up deleting some unused code as a result of the audit, which is always a good thing.
* AdaLogics contributed 3 additional fuzzers to the fuzzing test suite for Vitess.
* Vitess is not SLSA-compliant, because we do not yet generate provenance for our builds.

We are grateful to the [Cloud Native Computing Foundation](https://cncf.io) for sponsoring this audit, and to [OSTIF](https://ostif.org) and [AdaLogics](https://adalogics.com) for carrying it through.
Special thanks are due to Andrew Mason and Dirkjan Bussink for doing most of the remediation work, and to Adam Korczynski and David Korczyzski of ADA logics for conducting the audit.
Comment thread
deepthi marked this conversation as resolved.
Outdated

You can read the full audit report [here](../../files/VIT-03-report.pdf).
Comment thread
deepthi marked this conversation as resolved.
Outdated