Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

fastify-csrf

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.5npmAmendedPublished

    Lack of protection against cookie tossing attacks in fastify-csrf

    CVE-2021-29624 · GHSA-rc4q-9m69-gqp8

    Affected
    • npm fastify-csrf < 3.1.0
    Fixed in
    3.1.0· Vendor fix available
    Issue
    Impact Users that used fastify-csrf with the "double submit" mechanism using cookies with an application deployed across multiple subdomains, e.g. "heroku"-style platform as a service. Patches Version 3.1.0 of the fastify-csrf fixes it. See https://github.com/fastify/fastify-csrf/pull/51 and https://github.com/fastify/csrf/pull/2. The user of the module would need to supply a userInfo when generating the CSRF token to fully implement the protection on their end. This is needed only for applications hosted on different subdomains. Workarounds None available. References 1. https://cheatsheetseries.owasp.org/cheatsheets/Cross-SiteRequestForgeryPreventionCheatSheet.html 2. https://owasp.org/www-pdf-archive/DavidJohansson-DoubleDefeatofDouble-SubmitCookie.pdf Credits This vulnerability was found by Xhelal Likaj <xhelallikaj20@gmail.com. For more information If you have any questions or comments about this advisory: Open an issue in fastify-csrf Email us at hello@matteocollina.com

    Recommended action: Upgrade to 3.1.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. High, CVSS 8.8npmAmendedPublished

    Cross-site Request Forgery in fastify-csrf

    CVE-2020-28482 · GHSA-49wp-qq6x-g2rf

    Affected
    • npm fastify-csrf < 3.0.0
    Fixed in
    3.0.0· Vendor fix available
    Issue
    The package fastify-csrf before 3.0.0 has a set of issues that affect its ability to do CSRF protection. 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

    Recommended action: Upgrade to 3.0.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →