Mirror-registry: quay: server-side request forgery in proxy cache upstream registry configuration
- 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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
A flaw was found in Red Hat Quay's Proxy Cache configuration feature. When an organization administrator configures an upstream registry for proxy caching, Quay makes a network connection to the specified registry hostname without verifying that it points to a legitimate external service. An attacker with organization administrator privileges could supply a crafted hostname to force the Quay server to make requests to internal network services, cloud infrastructure endpoints, or other resources that should not be accessible from the Quay application.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- quay/quay-rhel8
Version range not reported
- quay/quay-rhel8
Version range not reported
- quay/quay-rhel8
Version range not reported
- quay/quay-rhel8
Version range not reported
- quay/quay-rhel8
Version range not reported
- quay/quay-rhel9
Version range not reported
- quay/quay-rhel9
Version range not reported
- quay/quay-rhel9
Version range not reported
- quay/quay-rhel8
Version range not reported
- openshift/mirror-registry-rhel8
Version range not reported
- openshift/mirror-registry-rhel8
Version range not reported