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.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Octavia | Openstack | * | 0.9.0 (excluding) |
| Red Hat OpenStack Platform 13.0 (Queens) | RedHat | openstack-tripleo-common-0:8.6.8-11.el7ost | * |
| Red Hat OpenStack Platform 14.0 (Rocky) | RedHat | openstack-tripleo-common-0:9.5.0-5.el7ost | * |
| Octavia | Ubuntu | cosmic | * |
| Octavia | Ubuntu | disco | * |
| Octavia | Ubuntu | eoan | * |
| Octavia | Ubuntu | groovy | * |
| Octavia | Ubuntu | hirsute | * |
| Octavia | Ubuntu | impish | * |
| Octavia | Ubuntu | kinetic | * |
| Octavia | Ubuntu | lunar | * |
| Octavia | Ubuntu | mantic | * |
| Octavia | Ubuntu | trusty | * |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: