Summary
openstack-swift was updated to fix three security issues.
These security issues were fixed:
- CVE-2015-1856: OpenStack Object Storage (Swift), when allow_version is configured, allowed remote authenticated users to delete the latest version of an object by leveraging listing access to the x-versions-location container (bsc#927793).
- CVE-2014-7960: OpenStack Object Storage (Swift) allowed remote authenticated users to bypass the max_meta_count and other metadata constraints via multiple crafted requests which exceed the limit when combined (bsc#900253).
- CVE-2015-5223: Information leak via Swift tempurls (bsc#942641).
Fixed packages 2
| Release | Package | Fixed in |
|---|---|---|
| SUSE · OpenStack Cloud 5 | openstack-swift | 2.1.0-11.1 |
| SUSE · OpenStack Cloud 5 | openstack-swift-doc | 2.1.0-11.1 |
Vulnerabilities 3
-
Medium —
OpenStack Swift metadata constraints are not correctly enforced
OpenStack Object Storage (Swift) before 2.2.0 allows remote authenticated users to bypass the max_meta_count and other metadata constraints via multiple crafted requests which exceed the limit when combined.
-
Medium —
OpenStack Swift Unauthorized delete of versioned Swift object
OpenStack Object Storage (Swift) before 2.3.0, when allow_version is configured, allows remote authenticated users to delete the latest version of an object by leveraging listing access to the x-versions-location container.
-
Medium —
OpenStack Object Storage (Swift) Sensitive Data Exposure
OpenStack Object Storage (Swift) before 2.4.0 allows attackers to obtain sensitive information via a PUT tempurl and a DLO object manifest that references an object in another container.