Quay cross-tenant credential theft in robot account listing
Project Quay quay · Red Hat Quay 3.10 · Red Hat Quay 3.12 · Red Hat Quay 3.14
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Project Quay quay |
| No fix yet |
| Red Hat Red Hat Quay 3.10 | — |
|
Project Quay quay · Red Hat Quay 3.10 · Red Hat Quay 3.12 · Red Hat Quay 3.14
| Product | Affected | Fixed in |
|---|---|---|
| Project Quay quay |
| No fix yet |
| Red Hat Red Hat Quay 3.10 | — |
|
| Red Hat Red Hat Quay 3.12 | — |
|
| Red Hat Red Hat Quay 3.14 | — |
|
| Red Hat Red Hat Quay 3.15 | — |
|
| Red Hat Red Hat Quay 3.16 | — |
|
| Red Hat Red Hat Quay 3.17 | — |
|
| Red Hat Red Hat Quay 3.18 | — |
|
| Red Hat Red Hat Quay 3.9 | — |
|
| Red Hat mirror registry for Red Hat OpenShift 2 | — | No fix yet |
| Red Hat Red Hat Quay 5 | — | No fix yet |
A flaw was found in Quay where the robot account listing function constructs a SQL LIKE pattern from user-controlled namespace names without escaping wildcard metacharacters. An attacker who creates a namespace containing an underscore character can match and retrieve robot accounts and their decrypted authentication tokens from other tenants' namespaces, leading to cross-tenant credential theft and unauthorized image operations.
From the CVE record · redhat
Quay’s robot account listing function does not escape SQL LIKE wildcards in user-controlled namespace names. An attacker who can create a namespace containing an underscore can retrieve robot accounts and decrypted authentication tokens from other tenants, enabling unauthorized image operations.
Operators of Project Quay quay, Red Hat Quay 3.9, 3.10, 3.12, and 3.14–3.18, or Red Hat mirror registry for Red Hat OpenShift 2 should check their deployments.