Red Hat Quay private image access via registry signing key rotation
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 Red Hat Quay. An unauthenticated client can obtain an anonymous registry token with an audience it controls, present that token to the service key rotation endpoint, and install its own approved signing key with no expiry. Registry tokens signed with that key are accepted for any repository, allowing read and write access to private images and replacement of repository tags.
From the CVE record · redhat
Red Hat Quay's service key rotation endpoint accepts an anonymous registry token with a client-controlled audience, allowing an unauthenticated client to install its own approved signing key with no expiry. Tokens signed with that key are accepted for any repository, allowing the client to read and write private images and replace repository tags without user interaction.
Operators of Project Quay quay, Red Hat Quay 3.9, 3.10, 3.12, and 3.14–3.18, and Red Hat mirror registry for Red Hat OpenShift 2 should check their deployments.