Skip to content
Fencer Vulns
medium 5.4

CVE-2023-3384 json

Quay: stored cross site scripting

published 2023-07-24 3 y ago modified 2026-11-01 8 d ago also EUVD-2023-44051

cvss
5.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 42%
public exploits
0
none known

Summary

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).

Patch / fix

  • Red Hat Red Hat Quay 3 v3.9.9-1, v3.9.9-2, v3.9.9-3, v3.9.9-5, v3.9.9-8

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-3384 updated cvss 5.4

quay: stored cross site scripting

  • Red Hat Quay v3 quay/quay-rhel8 v3.9.9-5, quay/clair-rhel8 v3.9.9-1, quay/quay-builder-rhel8 v3.9.9-3, quay/quay-operator-rhel8 v3.9.9-1, quay/quay-operator-bundle v3.9.9-8, quay/quay-bridge-operator-rhel8 v3.9.9-1, +4 more
    fixed: vendor fix RHBA-2024:11113

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
NVD 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Affected products

  • Red Hat Red Hat Quay 3

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.