LiveActive security incident?Get immediate response
CVE Record

CVE-2023-3384: Quay: stored cross site scripting

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

MediumCVSS 5.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-3384 is a stored cross-site scripting flaw in Red Hat Quay. Malicious script content can be carried in image labels and later execute when a user views affected registry content. Business risk is account/session impact and unauthorized actions within the user's browser context.

Executive priority

Treat as a moderate-priority remediation item. It is not described as actively exploited, but it affects a security-sensitive platform and can impact users who manage container images through Quay.

Technical view

Quay validates labels created through the UI and backend regex path, but the same validation is missing for labels that originate from an image. An attacker with the ability to publish a malicious image can create stored XSS. CVSS 3.1 is 5.4: network, low complexity, low privileges, user interaction required, changed scope.

Likely exposure

Exposure is likely limited to Red Hat Quay 3 deployments, including the quay/quay-rhel8 package, where users can publish or view images carrying image-provided labels. The source bundle does not provide fixed version ranges.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. Exploitation requires a malicious image to be published and a user to interact with affected Quay UI content.

Researcher notes

The vulnerability maps to CWE-79. The key data-flow issue is inconsistent validation: UI/backend-created labels are validated, image-origin labels are not. Version specificity and fixed releases are not included in the provided bundle, so remediation should be tied to Red Hat guidance.

Mitigation direction

  • Check Red Hat CVE and Bugzilla guidance for fixed builds or official mitigation.
  • Inventory Red Hat Quay 3 and quay/quay-rhel8 deployments.
  • Restrict image publishing rights to trusted users while assessing exposure.
  • Review registry content from untrusted publishers with heightened caution.
  • Monitor Red Hat advisories for patch or errata availability.

Validation and detection

  • Confirm whether Red Hat Quay 3 is deployed in your environment.
  • Identify whether quay/quay-rhel8 packages are in use.
  • Review who can publish images to public or shared registries.
  • Check whether untrusted image labels are displayed in Quay UI workflows.
  • Look for security alerts involving stored XSS or suspicious registry UI activity.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-3384 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N2.32.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2023-3384Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Red HatRed Hat Quay 3quay/quay-rhel8affected
Weakness

CWE details

CWE-79

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.