JWT 보안과 모범 사례
일반적인 공격을 방지하도록 JSON 웹 토큰(JWT)의 올바른 서명, 검증, 저장을 포함한 보안 고려 사항을 살펴봅니다.
JWT 보안과 모범 사례은(는) CoddyKit의 무료 Secure Coding & OWASP Top 10 for Backend 강의입니다. 이것은 4개 중 3번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 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
HttpOnlyflag prevents JavaScript (and thus XSS attacks) from accessing the token. Also useSecure(for HTTPS) andSameSiteattributes. - 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
algheader 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/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Secure Coding & OWASP Top 10 for Backend 강의 전체를 잠금 해제할 수 있습니다. Secure Coding & OWASP Top 10 for Backend 강의에는 총 4개의 강의가 포함되어 있습니다.
“JWT 보안과 모범 사례”에서 뭘 배우나요?
일반적인 공격을 방지하도록 JSON 웹 토큰(JWT)의 올바른 서명, 검증, 저장을 포함한 보안 고려 사항을 살펴봅니다. 브라우저에서 직접 실행하는 실습 코드로 Secure Coding & OWASP Top 10 for Backend을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.
Secure Coding & OWASP Top 10 for Backend을(를) 시작하는 데 경험이 필요한가요?
사전 경험은 필요하지 않습니다. CoddyKit의 Secure Coding & OWASP Top 10 for Backend은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 3번째 강의입니다.
“JWT 보안과 모범 사례” 강의는 얼마나 걸리나요?
대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.
이 Secure Coding & OWASP Top 10 for Backend 강의에서 코드를 작성하고 실행할 수 있나요?
네. 모든 Secure Coding & OWASP Top 10 for Backend 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.