CVE-2019-3895: High severity opendev octavia vulnerability
Description 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.
Mitigation To prevent this vulnerability: 1. Update Octavia's configuration setting (octavia.conf) to ampimageownerid = $UUIDOFSERVICEPROJECT on all Octavia nodes. 2. Enable the new configuration by restarting both octaviaworker and octaviahealthmanager.
Other sources
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.
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2019-3895?
CVE-2019-3895 is classified as a high severity vulnerability due to its access-control flaw in the Octavia service.
How do I fix CVE-2019-3895?
To fix CVE-2019-3895, upgrade to the recommended versions of the affected packages as specified in Red Hat's advisories.
What versions are affected by CVE-2019-3895?
CVE-2019-3895 affects openstack-tripleo-common versions up to 9, octavia versions up to 0.9.0, and specific versions of Red Hat OpenStack.
What kind of attack is possible with CVE-2019-3895?
An attacker could exploit CVE-2019-3895 to upload and run arbitrary amphorae images in the Octavia service.
Which OpenStack components are impacted by CVE-2019-3895?
The OpenStack components impacted by CVE-2019-3895 primarily include the Octavia service and the Red Hat OpenStack Platform.