fastify
Affected
- introduced
4.0.0, fixed4.10.2(semver)
Fixed versions
4.10.2
Fix
- Fixed version
4.10.2npm install [email protected]
Advisory
Also known as: CVE-2022-41919
Fastify: Incorrect Content-Type parsing can lead to CSRF attack
Impact
The attacker can use the incorrect Content-Type to bypass the Pre-Flight checking of fetch. fetch() requests with Content-Type’s essence as "application/x-www-form-urlencoded", "multipart/form-data", or "text/plain", could potentially be used to invoke routes that only accepts application/json content type, thus bypassing any CORS protection, and therefore they could lead to a Cross-Site Request Forgery attack.
Patches
For 4.x users, please update to at least 4.10.2
For 3.x users, please update to at least 3.29.4
Workarounds
Implement Cross-Site Request Forgery protection using `@fastify/csrf`.
References
Check out the HackerOne report: https://hackerone.com/reports/1763832.
For more information
Medium Basis: The source's own band: MODERATE
4.0.0, fixed 4.10.2 (semver)4.10.2
4.10.2npm install [email protected]3.0.0, fixed 3.29.4 (semver)3.29.4
3.29.4npm install [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