@fastify/passport
Affected
- introduced
0, fixed1.1.0(semver)
Fixed versions
1.1.0
Fix
- Fixed version
1.1.0npm install @fastify/[email protected]
Advisory
Also known as: CVE-2023-29020
CSRF token fixation in fastify-passport
The CSRF protection enforced by the @fastify/csrf-protection library, when combined with @fastify/passport, can be bypassed by network and same-site attackers.
Detailsfastify/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) andclearSessionIgnoreFields (default: ['session'])to clear all the session attributes by default, preserving those explicitly defined in clearSessionIgnoreFields.
Credits
Medium Basis: The source's own band: MODERATE
0, fixed 1.1.0 (semver)1.1.0
1.1.0npm install @fastify/[email protected]2.0.0, fixed 2.3.0 (semver)2.3.0
2.3.0npm install @fastify/[email protected]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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0