Vulnerabilities / JWT accepting none algorithm
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
↓
Severity
High
CWE Name
JWT accepting none algorithm
CWE ID
CWE-345
CVSS Score
7.5
Compliance
OWASP TOP10 -> A8
ISO27001 -> A.8.2, A.8.3, A.8.5, A.8.24, A.8.26
ISO27001 -> A.8.2, A.8.3, A.8.5, A.8.24, A.8.26
none
is accepted as a valid JWT verification algorithm in your tokens. With JWT algorithm none
there will be no integrity validation in the server. If the JWT is used to control access to the application, an attacker could take advantage of this vulnerability to forge a token and impersonate other users or even elevate privileges.
How to fix
-
The
none
can be set as the JWT verifying algorithm but, as the name describes it, it means no verification is actually performed on the JWT integrity. If the JWT is used to control access to the application, an attacker could take advantage of this vulnerability to forge a token and impersonate other users or even elevate privileges.