Skip to content

fix(extensions): re-validate catalog URL after redirects (HTTPS parity/security)#3524

Open
jawwad-ali wants to merge 1 commit into
github:mainfrom
jawwad-ali:fix/extensions-catalog-redirect-revalidate
Open

fix(extensions): re-validate catalog URL after redirects (HTTPS parity/security)#3524
jawwad-ali wants to merge 1 commit into
github:mainfrom
jawwad-ali:fix/extensions-catalog-redirect-revalidate

Conversation

@jawwad-ali

Copy link
Copy Markdown
Contributor

What

ExtensionCatalog._fetch_single_catalog fetched the catalog JSON and trusted it without re-validating the post-redirect URL — the same gap as in the presets catalog fetcher:

with self._open_url(entry.url, timeout=10) as response:
    catalog_data = json.loads(response.read())   # no response.geturl() check

_open_url follows redirects (stripping auth only on an HTTPS→HTTP downgrade), so an https:// catalog entry.url that 30x-redirects to http://attacker/catalog.json is still fetched and trusted. The payload supplies each extension's download_url and sha256, so an attacker-controlled redirected payload defeats sha256 verification and can drive installation of an arbitrary archive.

Fix

Re-validate response.geturl() after the redirect via _validate_catalog_url, mirroring integrations/catalog.py, workflows/catalog.py, bundler/services/adapters.py, and the presets catalog fetcher. This is the extensions sibling of the presets fix.

Test

test_fetch_single_catalog_revalidates_redirected_url: an HTTPS URL whose response.geturl() reports http:// is rejected with ExtensionError (fails before: no revalidation). Existing fetch-test mocks were completed to report geturl() like a real urllib response.

uv run pytest tests/test_extensions.py   # 354 passed, 3 skipped
uvx ruff check  # clean

🤖 Written with the assistance of Claude Code (AI). Bug self-found; fix/tests verified locally (fail-before / pass-after).

ExtensionCatalog._fetch_single_catalog opened the catalog URL and trusted the
payload without re-validating response.geturl() after redirects. _open_url
follows redirects (stripping auth only on an HTTPS->HTTP downgrade), so an
https:// catalog entry that 30x-redirects to http://attacker/... was still
fetched and trusted. The payload supplies each extension's download_url +
sha256, so a redirected payload can drive install of an arbitrary archive that
passes sha256 verification.

Add the post-redirect geturl() re-validation via _validate_catalog_url,
mirroring integrations/catalog.py, presets, workflows/catalog.py, and bundler
adapters. Sibling of the same fix in the presets catalog fetcher.

Test: an HTTPS URL whose response.geturl() reports http:// is rejected
(ExtensionError). Completed existing fetch-test mocks that predated this
behavior to report geturl() like a real urllib response.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jawwad-ali jawwad-ali requested a review from mnriem as a code owner July 14, 2026 17:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant