An access-control flaw was found in the Octavia service when the cloud platform was deployed using Red Hat OpenStack Platform Director. An attacker could cause new amphorae to run based on any arbitrary image. This meant that a remote attacker could upload a new amphorae image and, if requested to spawn new amphorae, Octavia would then pick up the compromised image.
An attacker may cause new amphorae to run based on any arbitrary
image. The attacker only needs to create an image in his/her own user
project, set same tag "amphora-image" and share it with the "service"
project. Upon request to spawn new amphorae, Octavia will now pick up
the compromised image.
Name: Carlos Goncalves (Red Hat)
Octavia was introduced in Red Hat OpenStack 12 and has been supported in newer versions. Upstream identified the issue and the code was merged into products delivered by Red Hat, however the configuration was not set by default. This CVE covers Red Hat OpenStack Director's default deployment of Octavia being insecure.
Related upstream flaw: https://bugs.launchpad.net/octavia/+bug/1620629
To prevent this vulnerability:
1. Update Octavia's configuration setting (octavia.conf) to `amp_image_owner_id = $UUID_OF_SERVICE_PROJECT` on all Octavia nodes.
2. Enable the new configuration by restarting both `octavia_worker` and `octavia_health_manager`.
Created openstack-tripleo-common tracking bugs for this issue:
Affects: openstack-rdo [bug 1714380]
Upstream tripleo-common bug: https://bugs.launchpad.net/tripleo/+bug/1830607
Upstream fix: https://github.com/openstack/tripleo-common/commit/e7c5eab712e0f70ecbc6d225d4766e0fe0f3f884