🛡️ Sentinel: [HIGH] Fix sensitive schema details leakage in public share exports#609
🛡️ Sentinel: [HIGH] Fix sensitive schema details leakage in public share exports#609seonghobae wants to merge 2 commits into
Conversation
|
👋 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 New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
There was a problem hiding this comment.
Pull request overview
OpenCode cannot approve yet because required coverage evidence did not pass.
Review outcome
1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence
-
Problem: The required coverage-evidence job result was
failure, so OpenCode cannot establish approval sufficiency for this head. -
Root cause: Automated approval is only valid when the same-head coverage-evidence job proves supported repository test suites passed and configured docstring gates passed or were advisory, or reports not applicable because no supported source files or package manifests exist. Missing, failed, skipped, unavailable, or unsupported-tooling test evidence is a blocker.
-
Fix: Install or configure the repository test/docstring evidence tooling when source files or package manifests exist, rerun the current-head coverage-evidence job, and approve only after it reports
successwith required evidence or explicit no-source not-applicable evidence. -
Regression test: Keep the approval branch checking
needs.coverage-evidence.result == successbefore posting APPROVE, and publish REQUEST_CHANGES when coverage-evidence blocker states such as cancelled, skipped, failed, unsupported-tooling, or below-100 evidence are present. -
Result: REQUEST_CHANGES
-
Reason: coverage-evidence result was
failure, so required test/docstring evidence was not proven for current headb4c31538293aca364784ab2031ea91fa4e2b3ac5. -
Head SHA:
b4c31538293aca364784ab2031ea91fa4e2b3ac5 -
Workflow run: 29764035553
-
Workflow attempt: 1
Coverage evidence
Coverage Decision
- Result: FAIL
- Test evidence: not proven passing
- Docstring evidence: not proven passing when configured
- Failure count: 1
Changed-File Evidence Map
flowchart LR
PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
Evidence --> S1["Changed file: sentinel.md"]
S1 --> I1["repository behavior"]
I1 --> R1["Review risk: Changed file: sentinel.md"]
R1 --> V1["required checks"]
Evidence --> S2["Backend: share.py"]
S2 --> I2["API and service runtime"]
I2 --> R2["Review risk: Backend: share.py"]
R2 --> V2["backend tests"]
OpenCode Review Overview
Pull request overviewOpenCode cannot approve yet because required coverage evidence did not pass. Review outcome1. HIGH .github/workflows/opencode-review.yml:1 - Coverage evidence did not prove required test/docstring evidence
Coverage evidenceCoverage Decision
Changed-File Evidence Mapflowchart LR
PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
Evidence --> S1["Changed file: sentinel.md"]
S1 --> I1["repository behavior"]
I1 --> R1["Review risk: Changed file: sentinel.md"]
R1 --> V1["required checks"]
Evidence --> S2["Backend: share.py"]
S2 --> I2["API and service runtime"]
I2 --> R2["Review risk: Backend: share.py"]
R2 --> V2["backend tests"]
|
🚨 Severity: HIGH
💡 Vulnerability: Publicly shared schema snapshot export routes (SQL, DB Reversing Spec, Index Design Spec) returned the entire JSON payload without redacting sensitive fields.
🎯 Impact: This could expose sensitive internal schema comments (
comment,relation_comment,column_comment) or sensitive data inexample_valuefields to users with access to public share links.🔧 Fix: Updated the export endpoints in
backend/app/api/share.pyto recursively redact thesnapshot_jsonpayload using the existing_redact_sensitive_snapshot_fieldsutility before generating the exports.✅ Verification: Ran all backend (
pytest) and frontend (pnpm test) suites. All 560 tests successfully pass without regressions.PR created automatically by Jules for task 12835962072319285078 started by @seonghobae