GHSA-j5qp-p44g-2m49
GHSA-j5qp-p44g-2m49 · @asymmetric-effort/specifyjs: No redirect target validation in secureFetch
This page contains facts from public vulnerability sources. Check the original advisory before updating.
## Finding **Location**: `core/src/shared/secure-fetch.ts` `assertSecureUrl` validated only the initial request URL. The `fetch()` API follows redirects by default (up to 20 hops). A request to a valid `https://` URL could redirect to `http://internal-service/` or other unvalidated destinations. ## Status **Fixed in v0.2.136** — `secureFetch` now defaults to `redirect: 'error'` which rejects any redirect. Callers can override with `{ redirect: 'follow' }` if they trust the target.
CVSS 6.9 · Medium · Fix available
- Published
- Updated
Stack: node
Affected products and versions
@asymmetric-effort/specifyjs npm
- Affected ranges
- SEMVER: < 0.2.136
Update to 0.2.136