yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Also affects: nova/havana
   Importance: Undecided
       Status: New

** Changed in: nova/havana
       Status: New => Fix Committed

** Changed in: ossa
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1206081

Title:
  [OSSA 2013-029] Unchecked qcow2 root disk sizes DoS

Status in OpenStack Compute (Nova):
  Fix Committed
Status in OpenStack Compute (nova) folsom series:
  In Progress
Status in OpenStack Compute (nova) grizzly series:
  Fix Committed
Status in OpenStack Compute (nova) havana series:
  Fix Committed
Status in OpenStack Security Advisories:
  Fix Released

Bug description:
  When doing QA for SUSE on bug 1177830
  I found that the fix is incomplete,
  because it assumed that the cached image would be mostly sparse.

  However, I can easily create non-sparse small compressed qcow2 images
  with

  perl -e 'for(1..11000){print "x" x 1024000}' > img
  qemu-img convert -c -O qcow2 img img.qcow2
  glance image-create --name=11gb --is-public=True --disk-format=qcow2 --container-format=bare < img.qcow2
  nova boot --image 11gb --flavor m1.small testvm

  which (in Grizzly and Essex) results in one (or two in Essex) 11GB large files being created in /var/lib/nova/instances/_base/
  still allowing attackers to fill up disk space of compute nodes
  because the size check is only done after the uncompressing / caching

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1206081/+subscriptions