GHSA-3p65-76g6-3w7r: Distribution affected by pull-through cache credential exfiltration via www-authenticate bearer realm
hi guys,commit: 40594bd98e6d6ed993b5c6021c93fdf96d2e5851 (as-of 2026-01-31)
contact: GitHub Security Advisory (https://github.com/distribution/distribution/security/advisories/new)summaryin pull-through cache mode, distribution discovers token auth endpoints by parsing `WWW-Authenticate` challenges returned by the configured upstream registry. the `realm` URL from a bearer challenge is used without validating that it matches the upstream registry host. as a result, an attacker-controlled upstream (or an attacker with MitM position to the upstream) can cause distribution to send the configured upstream credentials via basic auth to an attacker-controlled `realm` URL.this is the same vulnerability class as CVE-2020-15157 (containerd), but in distribution’s pull-through cache proxy auth flow.severityHIGHnote: the baseline impact is credential disclosure of the configured upstream credentials. if a deployment uses broader credentials for upstream auth (for example cloud iam credentials), the downstream impact can be higher; i am not claiming this as default for all deployments.impactcredential exfiltration of the upstream authentication material configured for the pull-through cache.attacker starting positions that make this realistic:supply chain / configuration: an operator configures a proxy cache to use an upstream that becomes attacker-controlled (compromised registry, stale domain, or a malicious mirror)network: MitM on the upstream connection in environments where the upstream is reachable over insecure transport or a compromised network pathaffected components`registry/proxy/proxyauth.go:66-81` (`getAuthURLs`): extracts bearer `realm` from upstream `WWW-Authenticate` without validating destination`internal/client/auth/session.go:485-510` (`fetchToken`): uses the realm URL directly for token fetch`internal/client/auth/session.go:429-434` (`fetchTokenWithBasicAuth`): sends credentials via basic auth to the realm URLreproductionattachment: `poc.zip` (local harness) with canonical and control runs.the harness is local and does not contact a real registry: it uses two local HTTP servers (upstream + attacker token service) to demonstrate whether basic auth is sent to an attacker-chosen realm.expected output (excerpt):control output (excerpt):suggested remediationvalidate that the token `realm` destination is within the intended trust boundary before associating credentials with it or sending any authentication to it. one conservative option is strict same-host binding: only accept a realm whose host matches the configured upstream host.fix accepted whendistribution does not send configured upstream credentials to an attacker-chosen realm URLa regression test covers the canonical and blocked cases[addendum.md](https://github.com/user-attachments/files/24984637/addendum.md)
[poc.zip](https://github.com/user-attachments/files/24984638/poc.zip)
[PR_DESCRIPTION.md](https://github.com/user-attachments/files/24984639/PR_DESCRIPTION.md)
[RUNNABLE_POC.md](https://github.com/user-attachments/files/24984640/RUNNABLE_POC.md)best,
oleh
CVSS v3.1: 7.5