Advisory

GHSA-2ccf-ffrj-m4qw

Also known as: CVE-2023-29020

Summary

CSRF token fixation in fastify-passport

Details

The CSRF protection enforced by the @fastify/csrf-protection library, when combined with @fastify/passport, can be bypassed by network and same-site attackers.

Details
fastify/csrf-protection implements the synchronizer token pattern (using plugins @fastify/session and @fastify/secure-session) by storing a random value used for CSRF token generation in the _csrf attribute of a user's session.

The @fastify/passport library does not clear the session object upon authentication, preserving the _csrf attribute between pre-login and authenticated sessions. Consequently, CSRF tokens generated before authentication are still valid. Network and same-site attackers can thus obtain a CSRF token for their pre-session, fixate that pre-session in the victim's browser via cookie tossing, and then perform a CSRF attack after the victim authenticates.

Fix
As a solution, newer versions of @fastify/passport include the configuration options

  • clearSessionOnLogin (default: true) and
  • clearSessionIgnoreFields (default: ['session'])

to clear all the session attributes by default, preserving those explicitly defined in clearSessionIgnoreFields.

Credits

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2023-04-21 22:32 UTC
Modified
2026-09-10 03:49 UTC

Affected packages and fixes

@fastify/passport

npm · All systems

Affected

  • introduced 0, fixed 1.1.0 (semver)

Fixed versions

1.1.0

Fix

@fastify/passport

npm · All systems

Affected

  • introduced 2.0.0, fixed 2.3.0 (semver)

Fixed versions

2.3.0

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences