SSRF (Server-Side Request Forgery) in @isomorphic-git/cors-proxy (CVE-2021-23664)
Summary
SSRF in @isomorphic-git/cors-proxy (CVE-2021-23664). Confidential information can be exposed externally. Mitigation: upgrade to 2.7.1 or later.
Original description
The description as published by the source.
The package @isomorphic-git/cors-proxy before 2.7.1 is vulnerable to Server-side Request Forgery (SSRF) due to missing sanitization and validation of the redirection action in middleware.js.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-23664 has been found in @isomorphic-git/cors-proxy.
Confidential information can be exposed externally.
What to do: upgrade @isomorphic-git/cors-proxy to 2.7.1 or later.
If unsure, ask your IT team or search "@isomorphic-git/cors-proxy CVE-2021-23664" on the vendor's site.
CVE-2021-23664 (@isomorphic-git/cors-proxy) — CWE-918
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.7.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in @isomorphic-git/cors-proxy.
Check the vendor advisory for the affected versions of @isomorphic-git/cors-proxy.
Severity: ?. Confidential information can be exposed externally.
Update to 2.7.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@isomorphic-git/cors-proxy' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@isomorphic-git/cors-proxy' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@isomorphic-git/cors-proxyを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @isomorphic-git/cors-proxy to 2.7.1ステージング環境で 2.7.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web snyk.io