How to fix: jwt.verify called with an empty or undefined secret
jwt.verify(token, '') or jwt.verify(token, undefined) passes an empty or missing key as the signing secret. Depending on the library and algorithm, this can let a token signed with a predictable or empty key pass verification.
Why it matters
Tokens forged by attackers with a known-empty or predictable secret pass verification and grant arbitrary identities or privileges.
The `code-jwt-verify-no-secret` check verifies that the server does not expose the `jwt-verify-no-secret` weakness in the code category. The detection runs against the response headers, body, or auxiliary probes (DNS, TLS, async fetch) as appropriate.
How to fix it
- 1Always pass an explicit secret or public key plus algorithms: ['HS256'] or ['RS256'].
- 2Reject tokens whose alg is 'none'.
- 3Centralize verification in a single middleware to enforce consistent options.
Code examples
Always pass a real secret/key to jwt.verify()
import jwt from "jsonwebtoken";
// BAD: an empty or undefined secret is a weak/predictable signing key
// jwt.verify(token, '');
// jwt.verify(token, undefined);
// GOOD: always supply the secret and restrict algorithms
const payload = jwt.verify(token, process.env.JWT_SECRET!, {
algorithms: ["HS256"], // reject RS256, none, etc.
}) as { sub: string; role: string };References
Detected automatically by VulnRadar. The check id is code-jwt-verify-no-secret, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is jwt.verify called with an empty or undefined secret?
- VulnRadar rates this critical severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id code-jwt-verify-no-secret, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does jwt.verify called with an empty or undefined secret map to?
- It maps to CWE-347. In the OWASP Top 10 it falls under A02:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.