Security Enhancement: Accessing mysql-proxy using a client or backend with a MySQL protocol less than MySQL 5.0 would result in mysql-proxy aborting with an assertion. This is because mysql-proxy only supports MySQL Protocol 5.0 or higher. The proxy will now report a fault. (Bug#31419)

MySQL Proxy would be configured with the LUA_PATH and LUA_CPATHn directory locations according to the build, not execution, host. In addition, during installation, certain Lua source files could be installed into the incorrect locations. (Bug#44877, Bug#44497)

Using mysql-proxy with very large return datasets from queries, with or without manipulate of the dataset within the Lua engine could cause a crash. (Bug#39332)

If a submitted packet was smaller than expected by the protocol, MySQL Proxy would terminate. (Bug#36743)

When using mysql-proxy in a master-master replication scenario, a failure in one of the replication masters would fail to be identified by the proxy and connections would not be redirected to the other master. (Bug#35295)