Secure Coding & OWASP Top 10 for Backend · 课时

JWT 安全与最佳实践

探索 JSON Web Token（JWT）涉及的安全注意事项，包括正确的签名、验证和存储，以防止常见攻击。

第 3 / 4 课12 个步骤

JWT 安全与最佳实践 是 CoddyKit 上的免费 Secure Coding & OWASP Top 10 for Backend 课时。这是第 3 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 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.

免费开始

用 AI 导师学习 Secure Coding & OWASP Top 10 for Backend — 免费

在浏览器中编写并运行真实代码，获得全天候 AI 导师的即时帮助，并在网页或应用中继续学习。

课程: 12
课程: 48

免费开始学习查看完整课程

常见问题解答

「JWT 安全与最佳实践」课时是免费的吗？

是的 — 「JWT 安全与最佳实践」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Secure Coding & OWASP Top 10 for Backend 课程的其余内容，请升级到 CoddyKit PRO。 Secure Coding & OWASP Top 10 for Backend 课程共包含 4 节课。

「JWT 安全与最佳实践」这节课中我会学到什么？

探索 JSON Web Token（JWT）涉及的安全注意事项，包括正确的签名、验证和存储，以防止常见攻击。你通过在浏览器中直接运行的动手代码来练习 Secure Coding & OWASP Top 10 for Backend，全天候 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