Packages / @fastify/busboy / Security
@fastify/busboy vulnerable to Denial of Service via oversized multipart boundary
Affected releases · @fastify/busboy
- 3.x3.1.0 – 3.2.0Fixed in 3.2.1
On 3.x, the newest line:
npm install @fastify/busboy@3.2.1Every release on a timeline
Not affected
1.0.0 – 3.0.0
8 releases
Affected
3.1.0 – 3.2.0
3 releases
Fixed
3.2.1 – 3.2.6
6 releases, latest
What happens
Impact
Versions of @fastify/busboy from 3.1.0 and prior to 3.2.1 are vulnerable to a Denial of Service. The vendored streaming multipart search stores its default skip distance in a Uint8Array(256). A multipart boundary of exactly 252 bytes makes the search needle 256 bytes, and the table entry wraps to zero, so a crafted request keeps the search in a CPU-bound loop and stalls the Node.js event loop. An unauthenticated client can trigger this with a single small request. Applications that use @fastify/busboy to parse multipart/form-data, directly or through @fastify/multipart, are affected.
Patches
Fixed in version 3.2.1.
Workarounds
Validate the multipart boundary before parsing and reject any boundary longer than the RFC 2046 limit of 70 characters (for example at a reverse proxy or in an onRequest hook). Upgrading to 3.2.1 removes the issue.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.