OpenStack Blazar
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.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.1high · scored by CNA · CWE-862
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
OpenStack Blazar
- >= 1.0.0, < 15.1.1
- >= 16.0.0, < 16.0.1
- >= 17.0.0, < 17.0.1
Fixed in 15.1.1, 16.0.1, 17.0.1
Mitigation
Upgrade Blazar to 15.1.1 or 16.0.1 or 17.0.1 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.