Advisory

GHSA-j5qp-p44g-2m49

Also known as: None

Summary

@asymmetric-effort/specifyjs: No redirect target validation in secureFetch

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-07-02 19:08 UTC
Modified
2026-09-10 03:51 UTC

Affected packages and fixes

@asymmetric-effort/specifyjs

npm · All systems

Affected

  • introduced 0, fixed 0.2.136 (semver)

Fixed versions

0.2.136

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences