🛡️ Sentinel: sanitize exception messages in boundary handlers#82
🛡️ Sentinel: sanitize exception messages in boundary handlers#82google-labs-jules[bot] wants to merge 1 commit into
Conversation
Remove user-controlled input from error messages returned to clients in GraphQL resolvers and Bedrock Agent tools to prevent information leakage and reflected input vulnerabilities.
|
👋 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. |
1 participant
🚨 Severity: MEDIUM
💡 Vulnerability: Information exposure through error messages. Boundary handlers were echoing back user-provided identifiers in error strings.
🎯 Impact: Malicious actors could use reflected input for injection attacks or discover internal state through verbose error messages.
🔧 Fix: Replaced specific error messages with generic ones in GraphQL and Bedrock Agent templates. Detailed errors remain available in internal logs.
✅ Verification: Verified via updated tests in tests/agent/test_handler.py and passing full test suite.
PR created automatically by Jules for task 8983509524646435803 started by @amrabed