🛡️ Sentinel: [CRITICAL] ERD DDL 생성 시 SQL 인젝션 방지

[seonghobae]

🚨 Severity: CRITICAL
💡 Vulnerability: ERD 도구에서 DDL을 생성할 때, 컬럼 타입 문자열에 세미콜론(;)을 포함시켜 기존 문장을 종료하고 악의적인 SQL 문(DROP TABLE 등)을 삽입할 수 있는 SQL 인젝션 취약점이 존재했습니다.
🎯 Impact: 악의적인 사용자가 스키마 생성 기능을 악용하여 데이터베이스를 임의로 조작하거나 파괴할 수 있습니다.
🔧 Fix: 컬럼 타입 문자열에 구문 종결자(세미콜론)가 포함되어 있는지 검사하고 차단하는 assertNoStatementTerminator 헬퍼 함수를 추가하여 SQL 인젝션을 방지했습니다.
✅ Verification: erd.test.ts에 세미콜론이 포함된 컬럼 타입 추가 시 예외가 발생하는지 확인하는 테스트 코드를 추가했으며, 모든 테스트가 정상 통과하는 것을 확인했습니다.

---

PR created automatically by Jules for task 15134268217133873559 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: 21 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: 1f90ac47-7154-4ef8-acd4-ed950bed21dd

📥 Commits

Reviewing files that changed from the base of the PR and between 085aea3 and 57d8f3d.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (4)

• .jules/sentinel.md
• package.json
• packages/web/src/lib/erd.test.ts
• packages/web/src/lib/erd.ts

---

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

[seonghobae]

Superseded by #397. The replacement is rebased onto the newer developmental line and closes the same ERD DDL-injection boundary more completely: instead of only rejecting semicolons, it uses positive SQL-type/default grammar validation, validates identifiers/foreign-key inputs, snapshots caller-owned model state to prevent post-validation mutation, and adds broader adversarial regression coverage. Keeping both PRs open creates a competing security-fix path and stale-base review noise, so this narrower predecessor is being closed without reusing its checks or reviews.

[google-labs-jules]

Superseded by #397. The replacement is rebased onto the newer developmental line and closes the same ERD DDL-injection boundary more completely: instead of only rejecting semicolons, it uses positive SQL-type/default grammar validation, validates identifiers/foreign-key inputs, snapshots caller-owned model state to prevent post-validation mutation, and adds broader adversarial regression coverage. Keeping both PRs open creates a competing security-fix path and stale-base review noise, so this narrower predecessor is being closed without reusing its checks or reviews.

Understood. Acknowledging that this work is now obsolete and stopping work on this task.