OpenStack Octavia vulnerabilities

In OpenStack Octavia before 18.0.1, the Amphora provider driver did not validate the listener and pool tls_ciphers field for control characters. The value is written verbatim into the HAProxy configuration generated on the amphora, allowing an authenticated project member who owns a TLS-enabled load balancer to embed a newline and inject arbitrary HAProxy configuration directives.

In OpenStack Octavia before 18.0.1, the Amphora provider driver did not reject control characters in the L7 policy redirect_url and redirect_prefix fields. The RFC 3986 URL validator percent-encodes control characters before validating, so newlines passed structural checks, but Octavia stored and wrote the raw unencoded value directly into the HAProxy configuration generated on the amphora.

OpenStack Octavia through 18.0.0 mishandles QoS policy authorization. By associating another project's QoS policy with an amphora, an authenticated user may prevent deletion of that policy.