Secure Coding & OWASP Top 10 for Backend · レッスン

JWTのセキュリティとベストプラクティス

一般的な攻撃を防ぐため、JSON Web Tokens（JWT）の適切な署名、検証、保存など、セキュリティ上の留意点を学びます。

「JWTのセキュリティとベストプラクティス」はCoddyKit上の無料Secure Coding & OWASP Top 10 for Backendレッスンです。これはレッスン3/4です。下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。これはSecure Coding & OWASP Top 10 for Backend学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Secure Coding & OWASP Top 10 for Backendコースには全4レッスンが含まれています。

このレッスンの一部はまだ翻訳されておらず、英語で表示されています。

Intro to JWT Security

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.

Quick Look: JWT Structure

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.

Why Sign a JWT?

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.

Signing: Symmetric vs. Asymmetric

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.

Generating a Signed JWT (HS256)

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.

import io.jsonwebtoken.Jwts;
import io.jsonwebtoken.SignatureAlgorithm;
import java.util.Date;
import javax.crypto.spec.SecretKeySpec;
import javax.xml.bind.DatatypeConverter;
import java.security.Key;

public class Main {
  public static void main(String[] args) {
    // A strong, unique secret key is crucial for security
    String secretString = "yourSuperSecretKeyThatIsVeryLongAndRandom12345!"; 
    byte[] apiKeySecretBytes = DatatypeConverter.parseBase64Binary(secretString);
    Key signingKey = new SecretKeySpec(apiKeySecretBytes, SignatureAlgorithm.HS256.getJcaName());

    String jwt = Jwts.builder()
        .setSubject("user123")
        .setIssuedAt(new Date(System.currentTimeMillis()))
        .setExpiration(new Date(System.currentTimeMillis() + 60 * 1000)) // 1 minute expiry
        .signWith(signingKey, SignatureAlgorithm.HS256)
        .compact();

    System.out.println("Generated JWT: " + jwt);
  }
}

Verifying the JWT Signature

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!

Validating JWT Claims

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.

Validating a JWT (HS256)

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

import io.jsonwebtoken.Jwts;
import io.jsonwebtoken.SignatureAlgorithm;
import io.jsonwebtoken.ExpiredJwtException;
import io.jsonwebtoken.MalformedJwtException;
import io.jsonwebtoken.SignatureException;
import io.jsonwebtoken.UnsupportedJwtException;
import java.util.Date;
import javax.crypto.spec.SecretKeySpec;
import javax.xml.bind.DatatypeConverter;
import java.security.Key;

public class Main {
  public static void main(String[] args) {
    String secretString = "yourSuperSecretKeyThatIsVeryLongAndRandom12345!";
    byte[] apiKeySecretBytes = DatatypeConverter.parseBase64Binary(secretString);
    Key signingKey = new SecretKeySpec(apiKeySecretBytes, SignatureAlgorithm.HS256.getJcaName());

    // --- Generate a token first (for demonstration) ---
    String jwtToValidate = Jwts.builder()
        .setSubject("user123")
        .setIssuedAt(new Date(System.currentTimeMillis()))
        .setExpiration(new Date(System.currentTimeMillis() + 60 * 1000)) // 1 min expiry
        .signWith(signingKey, SignatureAlgorithm.HS256)
        .compact();
    System.out.println("Generated JWT for validation: " + jwtToValidate);

    // --- Now validate it ---
    try {
      Jwts.parserBuilder()
          .setSigningKey(signingKey)
          .build()
          .parseClaimsJws(jwtToValidate);
      System.out.println("JWT is valid!");
    } catch (ExpiredJwtException e) {
      System.out.println("JWT validation failed: Token is expired!");
    } catch (MalformedJwtException | SignatureException | UnsupportedJwtException | IllegalArgumentException e) {
      System.out.println("JWT validation failed: Invalid token or signature. Reason: " + e.getMessage());
    }
  }
}

Securely Storing JWTs

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.

Common Attacks & Mitigations

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.

JWT Security Check

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.

Recap: Secure JWTs

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.

よくある質問

「JWTのセキュリティとベストプラクティス」レッスンは無料ですか？

はい。「JWTのセキュリティとベストプラクティス」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Secure Coding & OWASP Top 10 for Backendコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Secure Coding & OWASP Top 10 for Backendコースには全4レッスンが含まれています。

「JWTのセキュリティとベストプラクティス」で何を学びますか？

一般的な攻撃を防ぐため、JSON Web Tokens（JWT）の適切な署名、検証、保存など、セキュリティ上の留意点を学びます。ブラウザで直接実行するハンズオンコードでSecure Coding & OWASP Top 10 for Backendを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

Secure Coding & OWASP Top 10 for Backendを始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのSecure Coding & OWASP Top 10 for Backendは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。これはレッスン3/4です。

「JWTのセキュリティとベストプラクティス」レッスンにはどのくらい時間がかかりますか？

ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このSecure Coding & OWASP Top 10 for Backendレッスンでコードを書いて実行できますか？

はい。すべてのSecure Coding & OWASP Top 10 for Backendレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

← Secure Coding & OWASP Top 10 for Backendに戻る