@asymmetric-effort/specifyjs: No redirect target validation in secureFetch
Priority LOW 38CWE-918Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
## 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.
Why it matters now
Fix Fixed @asymmetric-effort/specifyjs (npm): 0.2.136
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | @asymmetric-effort/specifyjs (npm) | before 0.2.136 | 0.2.136 | Patch available | GHSA-j5qp-p44g-2m49 |
- @asymmetric-effort/specifyjs (npm) Vendor— Affected before 0.2.136 Fixed in 0.2.136 Patch available GHSA-j5qp-p44g-2m49
Remediation
- Fix · GHSA-j5qp-p44g-2m49 @asymmetric-effort/specifyjs (npm) Fixed in 0.2.136 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-j5qp-p44g-2m49
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences