3.9 KiB
Redirect header dependency patch
Baseline A3 a1149f0d, isolated codex/follow-redirects-patch, E:/Storage/Projects/Active/temp docs/jobjakt-local-build/next-security-patch. Source d60a333.
Locked follow-redirects1.16.1 matches GHSA-mrwp-f3q8-3g9p. The reviewed advisory describes custom-header leakage when the caller supplies sensitiveHeaders from another JavaScript realm; it names1.16.2 as patched. It explicitly does not establish an Axios1.20.0 exploit because Axios normalises this option. Do not claim a demonstrated Jobjakt/Axios exploit or production credential disclosure from this dependency finding.
Official registry latest1.16.3 satisfies Axios's existing^1.16.0 range, requires Node>=4 and has no install hook. The lock change affects exactly one package entry (1.16.1→1.16.3 and its resolved URL/integrity), no unrelated dependency updates/additions/removals or new override. Package.json only adds the permanent test:redirect-security command; no dependency declarations change.
Reproduction and verification
- Original installed1.16.1: same-realm control passed, cross-realm case FAILED and forwarded the synthetic custom key. Two ephemeral loopback HTTP servers only; built-in Authorization/Cookie and harmless-header assertions retained. No real credentials, internet target or production service.
- Ordinary npm install unexpectedly left installed1.16.1 despite lock1.16.3; a second test still FAILED. This result is retained and is not patched-version evidence. A fresh isolated
npm ci --ignore-scriptsthen installed verified1.16.3. No allowScripts policy changed or hooks approved. The package is pure JavaScript; other installation environments remain unqualified. - PASSED: both same/cross-realm tests on verified1.16.3, including
npm run test:redirect-security; each proves custom/auth/cookie stripping with unrelated header retained. The repeated command overlaps the two cases, not four tests. Tests remain outside JSDOM intentionally and are explicitly runnable via npm. - PASSED: ordinary Next16.4.6 compile/TypeScript/static export after fresh locked install, scoped test lint and source diff check. Initial CommonJS test lint failed under existing no-require-imports; converted to ES modules without a suppression/config change. Earlier build after ordinary install is not used to qualify installed1.16.3.
- Full fresh npm audit FAILED exit1:49 findings,7 moderate/42 high/0 critical; neither next nor follow-redirects appears. Prior full audit50 is historical and separately retained.
npm audit --omit=dev --package-lock-onlyPASSED exit0 with zero returned production-tree findings. Omission of dev dependencies is a separate scope, not suppression or whole supply-chain clearance. - NOT RUN: full frontend Jest rerun (Node-only transitive patch and explicit regression), backend, hosted CI, browser/provider/model/native-device/AT, real-service exploit, integrated security/recovery/release. Previous A3 browser evidence is source-bound and not newly executed here. Canonical Career Profile, revisions, tenant/session/permission enforcement, routes, UI/document language and PDF rendering have no source changes.
Evidence and continuation
Receipts bind committed package/lock/test and UTF8/LF-readable artifacts to exact native gzip hashes; native Windows UTF16 logs remain recoverable. Failed tests/setup/install mismatch are retained alongside final results. Publish/ref-verify this isolated branch before non-production A3 integration; rollback is reverting only this patch and locked reinstall, which restores the known affected dependency and is not a security-qualified release.
Remaining49 development-tool findings require compatible triage; do not apply suggested major downgrade fixes blindly. Formal independent integrated security and release gates remain open. No orchestrator, main merge or deployment.