Description
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.
Recommendation
Update the @asymmetric-effort/specifyjs package to the latest compatible version. Followings are version details:
- Affected version(s): < 0.2.136
- Patched version(s): 0.2.136
References
Could your website be exposed too?
SmartScanner can check your website for @asymmetric-effort/specifyjs: No redirect target validation in secureFetch and gives you actionable findings to investigate.
Start a free scanRelated Issues
- @asymmetric-effort/specifyjs: GraphQL gql tag allows metacharacter injection - Vulnerability
- @asymmetric-effort/specifyjs: Production console warnings may leak internal framework state - Vulnerability
- @asymmetric-effort/specifyjs: Localhost bypass incomplete (IPv6, 0.0.0.0, 127.x range) - Vulnerability
- @asymmetric-effort/specifyjs: `data:` URI allowed without size restriction - Vulnerability
You might also like:
See something that needs correcting? Let us knowUpdated July 02, 2026