Restricted HTTP client now covers all outbound requests
highrestrictedHTTPClient enabled(Inferred)restrictedHTTPClient enabledBefore the fix, outbound requests in these deployments could still reach private or other special-purpose addresses, exposing responses in publicly readable tracking or scanning errors and allowing content from OCI registries or git servers to be indexed and published. Chart values schemas are no longer validated during image extraction, so references in them are no longer fetched.
Show release-note lines
- kind: security
description: Enforce restricted HTTP client on all requestsgithub.com/artifacthub/hub/blob/v1.24.0/charts/artifact-hub/Chart.yamlThe `restrictedHTTPClient` setting did not apply to all outbound requests made by Artifact Hub. With the setting enabled, some requests could still reach private and other special purpose addresses, allowing server-side request forgery (CWE-918). This is fixed in version 1.24.0.github.com/artifacthub/hub/security/advisories/GHSA-78c6-r2j5-6856