🛡️ Sentinel: [HIGH] JWT crit 헤더 검증 로직 구현

[seonghobae]

🚨 Severity: HIGH\n💡 Vulnerability: JWT JOSE 헤더에 포함된 crit 파라미터가 서버에서 검증되지 않아, 의도치 않은/알 수 없는 중요 확장 파라미터를 사용한 토큰이 무시되고 인증을 통과할 수 있었습니다.\n🎯 Impact: 알 수 없는 확장을 통한 보안 우회 가능성 또는 침투 테스트(STRIX 등)에서의 심각한 보안 결함 보고\n🔧 Fix: auth.py의 _validate_jwt_header 함수에서 crit 헤더를 검사하도록 수정했습니다. 배열 형태인지 확인하고, 현재 시스템이 지원하는 crit 속성이 없으므로 배열이 비어있지 않은 경우 토큰을 거부(HTTP 401)합니다.\n✅ Verification: 관련 예외 처리 테스트 (backend/tests/test_auth_security.py)를 추가하였으며 100% 커버리지로 통과함을 확인했습니다.\n📝 .jules/sentinel.md 에 관련 보안 사항을 기록했습니다.

---

PR created automatically by Jules for task 16570658157523858824 started by @seonghobae

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 10 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 5027485e-f919-4722-b01a-7f4121f87598

📥 Commits

Reviewing files that changed from the base of the PR and between 72afe6d and 35bc90c.

📒 Files selected for processing (4)

• .jules/sentinel.md
• backend/app/auth.py
• backend/tests/test_auth_crit_rfc7515.py
• backend/tests/test_auth_security.py

---

_{Comment @coderabbitai help to get the list of available commands.}