Jeremey Stanley (jeremy) reports: Title: Resource limit circumvention in Nova private flavors Reporter: hzrandd (NetEase) Products: Nova Affects: All versions hzrandd from NetEase reported a resource limit circumvention vulnerability in Nova's handling of private flavors. Any tenant is able to show and boot any other tenant's private flavors by guessing a flavor ID. This not only exposes the flavor's name, memory and disk size, swap allocation, VCPU count and similar flavor properties, but potentially allows circumvention of any resource limits enforced through the os-flavor-access:is_public property. Havana (development branch) fix: https://review.openstack.org/34963 Grizzly fix: https://review.openstack.org/37992 Folsom fix: https://review.openstack.org/38318 Notes: This fix is included in the 2013.2.b2 development milestone and will appear in a future 2013.1.3 release.
This is now public: http://seclists.org/oss-sec/2013/q3/281
Created openstack-nova tracking bugs for this issue: Affects: fedora-all [bug 994809] Affects: epel-6 [bug 994810]
The previous fix was insufficient and did not fully fix the flaw, as noted here: https://bugs.launchpad.net/ossa/+bug/1212179 The patch to fully correct this flaw is here (I believe it would be in addition to previously-mentioned patches): https://github.com/openstack/nova/commit/4054cc4a22a1fea997dec76afb5646fd6c6ea6b9 This will require a second CVE for the incomplete fix; I've asked upstream to bring this up on the oss-security list.
(In reply to Vincent Danen from comment #5) > The previous fix was insufficient and did not fully fix the flaw, as noted > here: > > https://bugs.launchpad.net/ossa/+bug/1212179 > > The patch to fully correct this flaw is here (I believe it would be in > addition to previously-mentioned patches): > > https://github.com/openstack/nova/commit/ > 4054cc4a22a1fea997dec76afb5646fd6c6ea6b9 > > This will require a second CVE for the incomplete fix; I've asked upstream > to bring this up on the oss-security list. Assigned a CVE and created BZ 1000086
Acknowledgements: Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges hzrandd from NetEase as the original reporter. Upstream also acknowledges Ken'ichi Ohmichi from NEC for providing a corrected fix for this issue.
This issue has been addressed in following products: OpenStack 3 for RHEL 6 Via RHSA-2013:1199 https://rhn.redhat.com/errata/RHSA-2013-1199.html