JWT implementation in Rails is a common source of critical auth bypasses. Attackers exploit the 'none' algorithm flaw to forge tokens or brute-force weak HMAC secrets. To secure your stack, you must enforce algorithm whitelisting and use high-entropy keys managed via Rails credentials.

The Vulnerable Pattern

# DANGER: This implementation allows 'none' algorithm and skips verification
def decode_vulnerable(token)
  # Passing false as the third argument disables signature verification entirely
  # Attackers can change the header to {"alg": "none"} and modify the payload
  JWT.decode(token, nil, false)
end
DANGER: Weak, guessable secret
JWT.encode({ user_id: 1 }, ‘secret’, ‘HS256’)

The Secure Implementation

The 'none' algorithm attack works because the library trusts the 'alg' header sent by the attacker. By passing '{ algorithm: "HS256" }' as an option, you override the header and force the library to validate the signature using only the specified algorithm. Furthermore, 'verify=true' ensures the signature is checked against a strong secret stored in 'Rails.application.credentials', preventing token tampering and unauthorized privilege escalation.

# SECURE: Enforce verification and specific algorithm
def decode_secure(token)
  JWT.decode(
    token, 
    Rails.application.credentials.jwt_secret_key, 
    true, 
    { algorithm: 'HS256' }
  )
rescue JWT::DecodeError => e
  # Log failure and deny access
  nil
end