Description
In OpenStack Blazar before 17.0.1, the V2 lease listing operation (GET /v2/leases) returns leases for every project without enforcing project scoping or an administrator-only policy. Any authenticated user with access to the Blazar REST API can enumerate leases belonging to other tenants, exposing lease IDs, reservation IDs, resource IDs, and reservation metadata. The exposed lease IDs also enable the object-level authorization bypass tracked in the companion request, allowing an attacker to then modify or delete the enumerated leases.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| OpenStack | Blazar | 1.0.0 – < 15.1.1, 16.0.0 – < 16.0.1, 17.0.0 – < 17.0.1 | 15.1.1 |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | blazar | 18.0.0~rc1-3 | — |
| Debian 13 | blazar | No fix yet | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | blazar | No fix yet | — |
| Ubuntu 26.04 LTS | blazar | No fix yet | — |
References
- https://launchpad.net/bugs/2162719 issue-tracking