Packages / @fastify/busboy / Security
@fastify/busboy vulnerable to CRLF injection via multipart Content-Disposition filename and name
Affected releases · @fastify/busboy
- 3.x3.0.0 – 3.2.1Fixed in 3.2.2
- 2.x and older1.0.0 – 2.1.1No fix, no longer updated
On 3.x, the newest line:
npm install @fastify/busboy@3.2.2Every release on a timeline
Affected
3.0.0 – 3.2.1
5 releases
Fixed
3.2.2 – 3.2.6
5 releases, latest
Affected
2.0.0 – 2.1.1
3 releases
Affected
1.0.0 – 1.2.1
4 releases
What happens
Impact
@fastify/busboy 3.2.1 and earlier retains a bare carriage return or line feed inside the parsed Content-Disposition parameters returned to the application. The multipart header parser ends a header line only on the two-byte \r\n sequence, so a lone CR or LF embedded in a part header is carried verbatim into the filename and field name delivered by the file and field events. An application that forwards the supplied filename or name into a CR/LF-sensitive sink cannot anticipate the embedded control character.
An attacker who uploads a file whose filename or field name contains a bare CR or LF can pollute filenames on disk when the upload is saved under its original name, inject forged lines into logs, or inject headers on a downstream hop that does not re-validate CR/LF, such as object-storage metadata or a proxied backend. Applications using @fastify/busboy directly, or through @fastify/multipart and its consumers, are affected.
Patches
Upgrade to @fastify/busboy 3.2.2 or later.
Workarounds
Validate or strip carriage return and line feed characters from the filename and field name before using them in any filesystem, logging, or outbound-header context.
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.