What is CVE-2022-31142?

CVE-2022-31142 is a high-severity security vulnerability in fastify-bearer-auth (npm), affecting versions >= 5.0.1, <= 6.0.3. It is fixed in 7.0.2, 8.0.1.

How severe is CVE-2022-31142?

CVE-2022-31142 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2022-31142?

fastify-bearer-auth (npm) versions >= 5.0.1, <= 6.0.3; @fastify/bearer-auth (npm) versions < 7.0.2.

Is there a fix for CVE-2022-31142?

Yes. CVE-2022-31142 is fixed in 7.0.2, 8.0.1. Upgrade to this version or later.

Is CVE-2022-31142 exploitable, and should I be worried?

Whether CVE-2022-31142 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-31142 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2022-31142?

Upgrade: @fastify/bearer-auth to 7.0.2 or later, @fastify/bearer-auth to 8.0.1 or later.

CVE-2022-31142 in fastify-bearer-auth

Q: How severe is CVE-2022-31142?

CVE-2022-31142 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2022-31142?

fastify-bearer-auth (npm) versions >= 5.0.1, <= 6.0.3; @fastify/bearer-auth (npm) versions < 7.0.2.

Q: Is there a fix for CVE-2022-31142?

Yes. CVE-2022-31142 is fixed in 7.0.2, 8.0.1. Upgrade to this version or later.

Q: Is CVE-2022-31142 exploitable, and should I be worried?

Whether CVE-2022-31142 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-31142 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-31142?

Upgrade: @fastify/bearer-auth to 7.0.2 or later, @fastify/bearer-auth to 8.0.1 or later.

Summary

fastify-bearer-auth vulnerable to Timing Attack Vector

Workarounds

There are no workarounds. Update your dependencies.

References

https://hackerone.com/reports/1633287

For more information

If you have any questions or comments about this advisory:

Open an issue in https://github.com/fastify/fastify-bearer-auth
Email us at [email protected]

Impact

fastify-bearer-auth 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.

All versions of fastify-bearer-auth are also affected.

CVE-2022-31142 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (7.0.2, 8.0.1); upgrading removes the vulnerable code path.

Affected versions

fastify-bearer-auth (>= 5.0.1, <= 6.0.3) @fastify/bearer-auth (< 7.0.2) @fastify/bearer-auth (= 8.0.0)

Security releases

@fastify/bearer-auth → 7.0.2 (npm) @fastify/bearer-auth → 8.0.1 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

We released:

v8.0.1 with a fix for the Fastify v4 line
v7.0.2 with a fix for the Fastify v3 line

Frequently Asked Questions

What is CVE-2022-31142? CVE-2022-31142 is a high-severity security vulnerability in fastify-bearer-auth (npm), affecting versions >= 5.0.1, <= 6.0.3. It is fixed in 7.0.2, 8.0.1.
How severe is CVE-2022-31142? CVE-2022-31142 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2022-31142?
- fastify-bearer-auth (npm) (versions >= 5.0.1, <= 6.0.3)
- @fastify/bearer-auth (npm) (versions < 7.0.2)
Is there a fix for CVE-2022-31142? Yes. CVE-2022-31142 is fixed in 7.0.2, 8.0.1. Upgrade to this version or later.
Is CVE-2022-31142 exploitable, and should I be worried? Whether CVE-2022-31142 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-31142 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-31142?
- Upgrade @fastify/bearer-auth to 7.0.2 or later
- Upgrade @fastify/bearer-auth to 8.0.1 or later