In OpenStack Glance before 32.0.1, the location API does not validate destination hosts when adding an HTTP location to an image
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 30.2.1, 31.1.1 and 32.0.1.
In OpenStack Glance before 32.0.1, the location API does not validate destination hosts when adding an HTTP location to an image. Unlike the web-download import path, the location API only checks the URL scheme and does not apply the import_filtering_opts host restrictions. An authenticated user can add a location pointing to internal endpoints such as the cloud metadata service (169.254.169.254), and retrieve the response by downloading the image data. This affects both the new POST /v2/images/{id}/locations API and the old PATCH API when show_multiple_locations is enabled. Deployments with the HTTP store backend enabled are affected.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| OpenStack | >=16.0.0 <30.2.1, >=31.0.0 <31.1.1, >=32.0.0 <32.0.1 | 30.2.1, 31.1.1, 32.0.1 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket