Description
In OpenStack Zaqar before 22.0.2, WSGI transport mishandles the URL-Signature header. By sending a request with an empty URL-Signature header, an unauthenticated remote attacker who knows a target project's UUID may bypass both Keystone authentication and pre-signed URL verification, resulting in the ability to read, enumerate, create, and delete that project's queues, messages, claims, and subscriptions. By additionally claiming an administrative role, the attacker may also perform administrative operations, such as managing pools and flavors in admin_mode deployments. Only deployments using the WSGI transport with an authentication strategy configured are affected; the websocket transport is not affected.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| OpenStack | Zaqar | 1.0.0 – < 20.1.2, 21.0.0 – < 21.0.2, 22.0.0 – < 22.0.2 | 20.1.2 |
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 | zaqar | 23.0.0~rc1-3 | — |
| Debian 13 | zaqar | No fix yet | — |
| Debian 12 | zaqar | No fix yet | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | zaqar | No fix yet | — |
| Ubuntu 26.04 LTS | zaqar | No fix yet | — |
| Ubuntu 24.04 LTS | zaqar | No fix yet | — |
| Ubuntu 22.04 LTS | zaqar | No fix yet | — |
| Ubuntu 20.04 LTS | zaqar | No fix yet | — |
Show 2 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 18.04 LTS | zaqar | No fix yet | — |
| Ubuntu 16.04 LTS | zaqar | No fix yet | — |
References
- https://launchpad.net/bugs/2164987 issue-tracking