🛡️ Sentinel: [MEDIUM] Fix potential data leakage in error wrapping

[euxaristia]

🛡️ Sentinel: [MEDIUM] Fix potential data leakage in error wrapping

🚨 Severity: MEDIUM
💡 Vulnerability: When redacting sensitive information in error messages, using %w in fmt.Errorf wraps the original error object. This preserves the original unredacted error in memory, which could potentially be exposed later if the error is unwrapped using errors.Unwrap().
🎯 Impact: Sensitive information (such as paths containing sensitive user data or internal structure) could be leaked if the error is programmatically inspected or unwrapped downstream.
🔧 Fix: Changed %w to %s in fmt.Errorf calls within internal/cli/trust.go where the error is passed to redaction.ErrorMessage. This stringifies the inner error before redacting it, ensuring no unredacted error objects are passed around.
✅ Verification: Ran make test and make lint to ensure no regressions were introduced. Evaluated that downstream usages of this error (writeAppError) do not rely on errors.Is or errors.As matching the original error.

---

PR created automatically by Jules for task 10613422552832798974 started by @euxaristia

[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

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

Next review available in: 37 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: f42356cc-05d7-4a64-9418-bfa4e6c06efd

📥 Commits

Reviewing files that changed from the base of the PR and between a50574f and 84661f6.

📒 Files selected for processing (2)

• .jules/sentinel.md
• internal/cli/trust.go

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix-error-wrapping-redaction-10613422552832798974

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

Zero automated PR review

Verdict: No blockers found

Blockers

• None found.

Validation

• [pass] Diff hygiene: git diff --check
• [pass] Tests: go test ./...
• [pass] Build: go run ./cmd/zero-release build
• [pass] Smoke build: go run ./cmd/zero-release smoke

Scope

Head: 84661f6190e7
Changed files (2): .jules/sentinel.md, internal/cli/trust.go

This deterministic review checks validation status and basic diff hygiene. A human reviewer still owns product judgment and design quality.