🛡️ Sentinel: sanitize boundary handler error messages to avoid input reflection - #98
Conversation
…lection This commit sanitizes error responses in Bedrock Agent boundary handlers and exception messages in GraphQL boundary handlers. Raw user-provided identifiers and names are no longer reflected back to the client in response bodies or exceptions, mitigating risk of Cross-Site Scripting (XSS), input reflection, and information disclosure. Instead, generic, clear messages are returned while the specific identifiers are preserved in secure structured backend logs.
|
👋 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
This change sanitizes error responses in Bedrock Agent boundary handlers (
templates/agent/handler.py) and exception messages in GraphQL boundary handlers (templates/graphql/handler.py). Raw user-supplied strings are no longer reflected back to the client, preventing XSS, input reflection, and information disclosure. Generic messages are used instead, while preserving the specific identifiers in backend structured logs. Tests have been updated and run successfully.PR created automatically by Jules for task 4800964131040846981 started by @amrabed