[Openstack-security] [Bug 1739646] Related fix merged to nova (master)
OpenStack Infra
1739646 at bugs.launchpad.net
Fri Feb 15 02:18:12 UTC 2019
Reviewed: https://review.openstack.org/603910
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c8e65a5eb11515cfe70f8e6850b842cd594af6a5
Submitter: Zuul
Branch: master
commit c8e65a5eb11515cfe70f8e6850b842cd594af6a5
Author: Mohammed Naser <mnaser at vexxhost.com>
Date: Wed Sep 19 16:58:32 2018 -0400
Default zero disk flavor to RULE_ADMIN_API in Stein
The policy to allow booting instances without a volume when
root_gb is set to 0 was to be set to default to admin-only
in Stein.
Depends-On: I537c299b0cd400982189f35b31df74755422737e
Co-Authored-By: Matt Riedemann <mriedem.os at gmail.com>
Related-Bug: #1739646
Change-Id: I247402b6c4ff8a7cb71ef247a218478194d68ff8
--
You received this bug notification because you are a member of OpenStack
Security SIG, which is subscribed to OpenStack.
https://bugs.launchpad.net/bugs/1739646
Title:
Instance type with disk set to 0 can cause DoS
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) ocata series:
Fix Committed
Status in OpenStack Compute (nova) pike series:
Fix Committed
Status in OpenStack Compute (nova) queens series:
Fix Committed
Status in OpenStack Security Advisory:
Won't Fix
Status in OpenStack Security Notes:
New
Bug description:
In OpenStack at the moment, there is the ability to create instance
types with disk size 0. The API documentation states the following:
"The size of the root disk that will be created in GiB. If 0 the root
disk will be set to exactly the size of the image used to deploy the
instance. However, in this case filter scheduler cannot select the
compute host based on the virtual image size. Therefore, 0 should only
be used for volume booted instances or for testing purposes."
In a cloud environment where a deployer wants to offer boot-from-
volume instances, those instance types will be there. However, this
means that a user can upload an image of 4TB and boot small instances
where each one will have 4TB of storage, potentially exhausting the
disks local storage (or Ceph cluster if using Ceph for ephemeral
storage).
I'm not sure if this is a security issue or it should be published as
an advisory, but I believe there should be an option to disable the
feature of booting an instance with the exact size of the image used
so deployers have the ability/choice to provide boot-from-volume
instance types.
I can confirm this in our environment that if a customer creates an
instance with 200GB of ephemeral disk space, they can take an image of
it, then create an instance with that image on an instance type that
has no ephemeral disk space and get 200GB of disk.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1739646/+subscriptions
More information about the Openstack-security
mailing list