🛡️ Sentinel: [HIGH] projectId 경로 탐색(Path Traversal) 취약점 수정

[seonghobae]

🚨 Severity: HIGH
💡 Vulnerability: projectId 값에 대한 경로 탐색(Path Traversal) 공격 방어가 Python 백엔드(analysis-engine)에 누락되어 있었습니다. 악의적인 페이로드(예: ../etc/passwd)가 디렉토리 구성을 우회할 위험이 있었습니다.
🎯 Impact: 임시 워크스페이스 또는 캐시 디렉토리 범위를 벗어난 경로에 임의의 파일 읽기/쓰기가 발생할 가능성이 존재했습니다.
🔧 Fix: bandscope_analysis.api에 전달되는 projectId에 디렉토리 구분자(/, \)나 상위 디렉토리 참조(., ..)가 포함되어 있는지 검증하고, 발견 시 예외를 발생시키도록 보안 검증 로직을 추가했습니다.
✅ Verification: 테스트 슈트(test_api.py)에 관련 보안 검증을 테스트하는 케이스를 추가하여 100% 코드 커버리지를 유지하며 harness/quickcheck.sh를 통과했습니다.

---

PR created automatically by Jules for task 1375492852410334289 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: 28 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: 7df6bfe1-59ea-48fa-a3c5-b3562dac4ae0

📥 Commits

Reviewing files that changed from the base of the PR and between f8343f5 and 8472533.

⛔ Files ignored due to path filters (2)

• package-lock.json is excluded by !**/package-lock.json
• services/analysis-engine/uv.lock is excluded by !**/*.lock

📒 Files selected for processing (4)

• .jules/sentinel.md
• services/analysis-engine/pyproject.toml
• services/analysis-engine/src/bandscope_analysis/api.py
• services/analysis-engine/tests/test_api.py

---

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

[seonghobae]

Closing as closed-duplicate/superseded (path-traversal cluster) by autonomous product-completion loop.

Winner / disposition target: #727

Unique value from this cluster is consolidated there (projectId path guard + npm HIGH CVE pins + Foote novelty kernel sign). Remaining micro-duplicates do not land additional commercial readiness.

[seonghobae]

closed-closed-duplicate/superseded (path-traversal cluster) → #727