Fedora Account System
Red Hat Associate
Red Hat Customer
A flaw was found in Quay's repository notification webhook delivery path. WebhookMethod in notifications/notificationmethod.py validates user-supplied callback URLs using only a hostname string blocklist (HOSTNAME_BLACKLIST: localhost, 127.0.0.1, plus WEBHOOK_HOSTNAME_BLACKLIST). It does not resolve DNS or reject RFC 1918, loopback, link-local, or cloud-metadata destinations. Unlike mirror, proxy-cache, and export-log callback flows, this path does not call validate_external_registry_url() in util/security/ssrf.py. Delivery then uses requests.post() with the default allow_redirects=True, so a public URL that passes the name check can respond with a 302/307 to an internal address and the notification worker will follow it without re-validation. An authenticated repository administrator who can create webhook notifications can cause the Quay worker to issue HTTP requests to internal network locations, including cloud instance metadata endpoints where reachable, resulting in server-side request forgery.