Quay: stored cross site scripting
Red Hat Quay 3
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Red Hat Quay 3 | — |
|
| Red Hat Red Hat Quay 3 | — |
|
| Red Hat Red Hat Quay 3 | — |
|
| Red Hat Red Hat Quay 3 | — |
|
Red Hat Quay 3
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Red Hat Quay 3 | — |
|
| Red Hat Red Hat Quay 3 | — |
|
| Red Hat Red Hat Quay 3 | — |
|
| Red Hat Red Hat Quay 3 | — |
|
| Red Hat Red Hat Quay 3 | — |
|
| Red Hat Red Hat Quay 3 | — |
|
| Red Hat Red Hat Quay 3 | — |
|
| Red Hat Red Hat Quay 3 | — |
|
| Red Hat Red Hat Quay 3 | — |
|
| Red Hat Red Hat Quay 3 | — |
|
A flaw was found in the Quay registry. While the image labels created through Quay undergo validation both in the UI and backend by applying a regex (validation.py), the same validation is not performed when the label comes from an image. This flaw allows an attacker to publish a malicious image to a public registry containing a script that can be executed via Cross-site scripting (XSS).
From the CVE record · redhat
Quay validates labels created through its UI and backend, but not labels that come from an image. An attacker who can publish a malicious image to a public registry can use an image label to cause script execution through cross-site scripting. The input does not specify whether authentication or user interaction is required.
Teams running Red Hat Quay 3 should check their deployments.