First published: Fri Mar 22 2013(Updated: )
The v1 API in OpenStack Glance Essex (2012.1), Folsom (2012.2), and Grizzly, when using the single-tenant Swift or S3 store, reports the location field, which allows remote authenticated users to obtain the operator's backend credentials via a request for a cached image.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
pip/glance | <11.0.0a0 | 11.0.0a0 |
Glance | =v1 | |
OpenStack Essex | =2012.1 | |
OpenStack Folsom | =2012.2 | |
Amazon S3 | ||
OpenStack Swift3 | ||
All of | ||
Glance | =v1 | |
Any of | ||
OpenStack Essex | =2012.1 | |
OpenStack Folsom | =2012.2 | |
Any of | ||
Amazon S3 | ||
OpenStack Swift3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-1840 has a severity rating that can allow remote authenticated users to expose sensitive backend credentials.
To fix CVE-2013-1840, upgrade to OpenStack Glance version 11.0.0a0 or later.
CVE-2013-1840 affects OpenStack Glance versions from Essex (2012.1) and Folsom (2012.2) up to but not including version 11.0.0a0.
Yes, using the v1 API with S3 store in OpenStack can lead to risks associated with CVE-2013-1840.
Yes, CVE-2013-1840 is relevant to both OpenStack Essex (2012.1) and Folsom (2012.2) versions.