mediumVulnerability

GHSA-j5qp-p44g-2m49

## 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.

Properties

ghsa_id
GHSA-j5qp-p44g-2m49
severity
medium
summary
@asymmetric-effort/specifyjs: No redirect target validation in secureFetch
cve_id
GHSA-j5qp-p44g-2m49
is_ghsa_only
true
ghsa_published
2026-07-02T19:08:04Z
source_url
https://github.com/advisories/GHSA-j5qp-p44g-2m49
ghsa_updated
2026-07-02T19:08:05Z

Related Entities (4)

AFFECTS (1)

[Software]npm/@asymmetric-effort/specifyjs

HAS_WEAKNESS (1)

[Weakness]Server-Side Request Forgery (SSRF)

REPORTED_BY (1)

[Source]GitHub Advisory Database

VULNERABLE_TO (1)

[Software]npm/@asymmetric-effort/specifyjs

Explore deeper with Ninja Signal's threat intelligence graph

GHSA-j5qp-p44g-2m49 — Ninja Signal Threat Intelligence | Ninja Signal