Image data stays in store if image is deleted after creating image using import task (CVE-2015-3289)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
Undecided
|
Unassigned | ||
OpenStack Security Advisory |
Fix Released
|
Undecided
|
Tristan Cacqueray |
Bug Description
Image data stays in store if image is deleted after creating image using import task
Trying to delete image created using task api (import-from) image gets deleted from the database, but image data remains in the backend.
Steps to reproduce:
1. Create image using task api
$ curl -i -X POST -H 'User-Agent: python-
2. wait until image becomes active.
3. Confirm image is in active state.
$ glance image-list
4. Delete the image
$ glance image-delete <image-id>
5. Verify image-list does not show deleted image
$ glance image-list
Image gets deleted from the database but image data presents in the backend.
Note:
This issue is fixed in master by this patch https:/
This issue will be resolved by back-porting above patch to stable/kilo.
Affected branches: stable/kilo
CVE References
Changed in glance: | |
status: | New → Fix Released |
Attack scenario here is to create/delete a lot of images using import task and DoS the image backend by filling it up.