Potential Timing Attack Vector in @fastify/bearer-auth
fastify-bearer-auth
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| fastify-bearer-auth npm |
| No fix yet |
| @fastify/bearer-auth npm |
|
|
fastify-bearer-auth
| Product | Affected | Fixed in |
|---|---|---|
| fastify-bearer-auth npm |
| No fix yet |
| @fastify/bearer-auth npm |
|
|
@fastify/bearer-auth is a Fastify plugin to require bearer Authorization headers. @fastify/bearer-auth prior to versions 7.0.2 and 8.0.1 does not securely use crypto.timingSafeEqual. A malicious attacker could estimate the length of one valid bearer token. According to the corresponding RFC 6750, the bearer token has only base64 valid characters, reducing the range of characters for a brute force attack. Version 7.0.2 and 8.0.1 of @fastify/bearer-auth contain a patch. There are currently no known workarounds. The package fastify-bearer-auth, which covers versions 6.0.3 and prior, is also vulnerable starting at version 5.0.1. Users of fastify-bearer-auth should upgrade to a patched version of @fastify/bearer-auth.
From the CVE record · GitHub_M
The Fastify bearer-auth plugins do not securely use crypto.timingSafeEqual when checking bearer tokens. An attacker sending Authorization headers could estimate the length of a valid token, narrowing a brute-force search. The input does not specify any user interaction.
Check installations of npm fastify-bearer-auth versions 5.0.1 through 6.0.3 and @fastify/bearer-auth versions before 7.0.2 or from 8.0.0 to before 8.0.1.