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
{
"unresolved_ranges": [
{
"source": "CPE_RANGE",
"cpes": [
"cpe:2.3:a:fastify:fastify-csrf:*:*:*:*:*:node.js:*:*"
],
"vendor_product": "fastify:fastify-csrf",
"extracted_events": [
{
"fixed": "3.0.0"
}
]
}
]
}