Sicurezza e best practice per i JWT

JSON Web Tokens (JWTs) are popular for authentication and securely exchanging information between parties. They're compact and self-contained.

However, their self-contained nature means that security is paramount. Improper handling or validation of JWTs can lead to serious vulnerabilities in your backend applications.

A JWT consists of three parts, separated by dots:

• Header: Specifies the token type (JWT) and the signing algorithm (e.g., HS256, RS256).
• Payload: Contains claims – statements about an entity (like a user ID) and additional data (like roles, expiration time).
• Signature: Used to verify the token's integrity and authenticity.

Remember, the payload is encoded (Base64Url), not encrypted. Anyone can read the claims, so don't put sensitive data directly in the payload.

The signature is the most critical security component of a JWT. It's created by combining the encoded header, encoded payload, and a secret key (or private key for asymmetric algorithms).

The signature provides two key assurances:

• Integrity: Confirms that the token's header or payload hasn't been tampered with since it was issued.
• Authenticity: Verifies that the token was indeed created by the expected sender.

Without a valid signature, a token is untrustworthy, even if its claims look legitimate.

JWTs can be signed using different types of cryptographic algorithms:

• Symmetric (e.g., HS256): Uses a single, shared secret key for both signing and verification. It's faster and simpler, but the same key must be securely known by both the issuer and the verifier.
• Asymmetric (e.g., RS256): Uses a private key for signing and a public key for verification. More complex, but allows multiple parties to verify tokens using the public key without needing access to the sensitive private key.

Choose the algorithm based on your application's security requirements and key management capabilities.

Here's a basic Java example demonstrating how to create an HS256 signed JWT using a common library. Pay attention to how the secret key is utilized.

Upon receiving a JWT, your backend must always verify its signature before trusting any of its claims.

The verification process involves recalculating the signature using the token's header, payload, and the expected secret key (or public key). If the calculated signature doesn't match the one present in the token, the token has been tampered with or wasn't issued by a trusted source.

Any token with an invalid signature must be rejected immediately!

Beyond signature verification, it's essential to validate the claims within the JWT's payload. This helps prevent various attacks and ensures the token is used correctly:

• Expiration (exp): Check if the token has expired.
• Not Before (nbf): Ensure the token is not being used before its activation time.
• Issued At (iat): Understand when the token was issued.
• Issuer (iss): Verify that the token originated from a trusted entity.
• Audience (aud): Confirm the token is intended for your specific service or application.

Implement strict claim validation to prevent replay attacks and ensure proper context for token usage.

This Java example shows how to validate a JWT, checking both its signature and common claims like expiration. It also demonstrates handling common exceptions.

Where and how JWTs are stored on the client-side significantly impacts security:

• HTTP-only cookies: Generally recommended for access tokens. Setting the HttpOnly flag prevents JavaScript (and thus XSS attacks) from accessing the token. Also use Secure (for HTTPS) and SameSite attributes.
• Local Storage/Session Storage: Highly vulnerable to Cross-Site Scripting (XSS) attacks, as any JavaScript on the page can access these stores. Not recommended for storing sensitive JWTs that grant access to resources.

For refresh tokens, consider storing them in secure, HTTP-only cookies, while short-lived access tokens can be held in memory.

Be aware of these prevalent JWT attack vectors and how to mitigate them:

• "alg": "none" attack: Attackers try to change the algorithm in the header to "none". Your server must explicitly validate the alg header and reject "none" or any unexpected algorithms.
• Weak Secret Keys: Easily guessable or short secret keys make brute-forcing signatures trivial. Always use strong, random, and sufficiently long keys.
• No Expiration (exp) Claim: Tokens without an expiration can be used indefinitely. Always set a short expiration time for access tokens.
• Replay Attacks: Even with expiration, a valid token can be intercepted and replayed. Consider using a "JTI" (JWT ID) claim and a server-side blacklist for invalidated tokens.

A developer configured their backend to accept JWTs but forgot to explicitly specify a required signing algorithm during validation. An attacker sends a JWT with "alg": "none" in the header, and no signature.

We've covered the critical aspects of JWT security:

• JWTs must always be signed to ensure integrity and authenticity.
• Always validate the signature and all relevant claims (expiration, issuer, audience).
• Use strong, secret keys and appropriate signing algorithms (HS256, RS256).
• Store JWTs securely, preferably in HTTP-only, secure cookies for access tokens, and potentially in memory for short durations.
• Be vigilant against common attacks like the "alg": "none" vulnerability and implement explicit checks for the algorithm.

Proper implementation of these practices is key to leveraging JWTs securely in your backend applications.