High severityJavaScript / TypeScriptAuthentication & SecretsHIGH confidence
JWT Algorithm None
JWT verification allows the 'none' algorithm, which accepts unsigned tokens and defeats authentication.
Standards mapping
- OWASP Top 10
- A02:2021 - Cryptographic Failures
- OWASP ASVS
- V3.5.3 (L1)
Vulnerable vs. safe
Flagged by this check
const v1 = jwt.verify(token, secret, { algorithms: ["none"] });Passes - the safe pattern
const v2 = jwt.verify(token, secret, { algorithms: ["RS256"] });Why it matters & how to fix it
JWT verification allows the 'none' algorithm, which accepts unsigned tokens and defeats authentication. Restrict algorithms to a specific signing algorithm (e.g. ['RS256'] or ['HS256']).
References
Rule ID integsec-js-jwt-algorithm-none - engine: Opengrep - license: MIT - Copyright (c) IntegSec Inc.
TurboPentest runs this check automatically
Connect a GitHub repo and this check runs on every white-box pentest - AI-validated and reported with proof, from $99 per target.
Start a pentestRelated checks
- JavaScript / TypeScript - Authentication & SecretsHardcoded JWT Secret
- JavaScript / TypeScript - Authentication & SecretsHardcoded Secret
- JavaScript / TypeScript - Authentication & SecretsInsecure Cookie Flags
- JavaScript / TypeScript - Authentication & SecretsJWT Decode Without Verify
- JavaScript / TypeScript - Authentication & SecretsTLS Verification Disabled
- Python - Authentication & SecretsDjango Hardcoded Secret Key