Security Test: JWT algorithm confusion¶

Description¶

Default Severity: high

JWT algorithm confusion happens when a server blindly trusts the algorithm specified in a token, even if it's not the one it expects. This means an attacker could change the algorithm in the token header and trick the server into verifying the signature with the wrong key method, potentially allowing them to forge tokens and gain unauthorized access. Developers can fall into this trap by not strictly enforcing which algorithm should be used, leaving room for attackers to bypass proper validation. If left untreated, this vulnerability risks data breaches and compromised systems by letting attackers impersonate legitimate users or escalate privileges.

Configuration¶

Identifier: injection/jwt_alg_confusion

Examples¶

All configuration available:

checks:
  injection/jwt_alg_confusion:
    skip: false # default

Compliance and Standards¶