🛡️ Sentinel: [HIGH] Fix SQL injection & Object mutation vulnerability in ERD Model

[seonghobae]

🚨 Severity: HIGH\n💡 Vulnerability: SQL Injection via unchecked types and state mutation via exposed internal objects in ERDModel.\n🎯 Impact: Attackers could inject malicious SQL commands and manipulate internal state to bypass security restrictions.\n🔧 Fix: Added allowlist regex validation for SQL types, and applied deep copy using structuredClone for state accessors.\n✅ Verification: Checked vitest execution passing perfectly.

---

PR created automatically by Jules for task 9926514501401075835 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: 14 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: 13e75179-f534-488d-853b-933a5cb53940

📥 Commits

Reviewing files that changed from the base of the PR and between 4f8796e and 4ba675f.

📒 Files selected for processing (3)

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

---

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

[seonghobae]

Closing as superseded by #397. Both PRs target the same ERD SQL-type injection and mutable-state boundary from the same developmental base SHA, but #402's broad SAFE_SQL_TYPE token regex still admits grammar smuggling such as INTEGER PRIMARY KEY or TEXT NOT NULL. #397 is the hardened test-first repair path: it separates data-type grammar from constraints, restricts default expressions, snapshots caller-owned state, adds security doctoring/CHANGELOG evidence, and carries regression coverage for the structural bypasses. No checks or review evidence from this PR are transferred to #397.

[google-labs-jules]

Closing as superseded by #397. Both PRs target the same ERD SQL-type injection and mutable-state boundary from the same developmental base SHA, but #402's broad SAFE_SQL_TYPE token regex still admits grammar smuggling such as INTEGER PRIMARY KEY or TEXT NOT NULL. #397 is the hardened test-first repair path: it separates data-type grammar from constraints, restricts default expressions, snapshots caller-owned state, adds security doctoring/CHANGELOG evidence, and carries regression coverage for the structural bypasses. No checks or review evidence from this PR are transferred to #397.

Understood. Acknowledging that this work is now superseded by #397 and stopping work on this task.