CVE-2023-3384
Quay: stored cross site scripting
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
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).
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- quay/clair-rhel8
Version range not reported
- quay/quay-bridge-operator-bundle
Version range not reported
- quay/quay-bridge-operator-rhel8
Version range not reported
- quay/quay-builder-qemu-rhcos-rhel8
Version range not reported
- quay/quay-builder-rhel8
Version range not reported
- quay/quay-container-security-operator-bundle
Version range not reported
- quay/quay-container-security-operator-rhel8
Version range not reported
- quay/quay-operator-bundle
Version range not reported
- quay/quay-operator-rhel8
Version range not reported
- quay/quay-rhel8
Version range not reported