Cross-Site Request Forgery (CSRF) in fastify-csrf (CVE-2020-28482)
Summary
Vulnerability in fastify-csrf (CVE-2020-28482). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.0.0 or later.
Original description
The description as published by the source.
The package fastify-csrf before 3.0.0 has a set of issues that affect its ability to do CSRF protection.
- The generated cookie used insecure defaults, and did not have the httpOnly flag on:
cookieOpts: { path: '/', sameSite: true } - The CSRF token was available in the GET query parameter
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-2020-28482 has been found in fastify-csrf.
Successful exploitation can lead to full system takeover.
What to do: upgrade fastify-csrf to 3.0.0 or later.
If unsure, ask your IT team or search "fastify-csrf CVE-2020-28482" on the vendor's site.
CVE-2020-28482 (fastify-csrf) — CWE-352
Attack vector: remote (network-reachable) / unauthenticated
Patched: 3.0.0 — 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.
CSRF (CWE-352) exists in fastify-csrf.
Check the vendor advisory for the affected versions of fastify-csrf.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 3.0.0.
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 'fastify-csrf' . 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 'fastify-csrf' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
fastify-csrfを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade fastify-csrf to 3.0.0ステージング環境で 3.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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 github.com
- web snyk.io
- web npmjs.com