CVE-2020-28482 json
Cross-site Request Forgery (CSRF)
published 5y ago modified 4mo ago also GHSA-49wp-qq6x-g2rf , EUVD-2021-0487
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 62%
- public exploits
- 0
- none known
Summary
This affects the package fastify-csrf before 3.0.0. 1. The generated cookie used insecure defaults, and did not have the httpOnly flag on: cookieOpts: { path: '/', sameSite: true } 2. The CSRF token was available in the GET query parameter
Patch / fix
- npm fastify-csrf 3.0.0
- n/a fastify-csrf 3.0.0
- github.com/fastify/fastify-csrf@3c9de36 commit
- github.com/fastify/fastify-csrf#26 pull request
Is CVE-2020-28482 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.99% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | fastify-csrf | <3.0.0 |
3.0.0 |
Affected products
- n/a fastify-csrf
Classification
References
-
github.com
/fastify/fastify-csrf/pull/26
web, third-party-advisory
-
github.com
/fastify/fastify-csrf/commit/3c9de36e9e73ce0eda9207f84f2ac0243e1f5253
web
-
snyk.io
/vuln/SNYK-JS-FASTIFYCSRF-1062044
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-28482
advisory
-
github.com
/fastify/fastify-csrf
package
-
npmjs.com
/package/fastify-csrf
web
Sources
- CVE List CVE-2020-28482
- GitHub Advisory GHSA-49wp-qq6x-g2rf
- NVD CVE-2020-28482
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.