π‘οΈ Sentinel: [CRITICAL] Fix Internal Error Leakage via API Responses in MCP Server#254
Conversation
β¦in MCP Server Co-authored-by: davidruzicka <14172985+davidruzicka@users.noreply.github.com>
|
π 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. |
Codecov Reportβ
All modified and coverable lines are covered by tests. π’ Thoughts on this report? Let us know! |
π¨ Severity: CRITICAL
π‘ Vulnerability: The MCP server JSON-RPC handlers for
prompts/get,resources/read, andcompletion/completewere catching raw runtime and logic exceptions and leaking the un-sanitized errormessagestring directly to the client in theerror.messagefield of the JSON-RPC response.π― Impact: An attacker or regular client could receive sensitive internal server details, such as database error messages, paths, or service configuration specifics, increasing the attack surface.
π§ Fix: The catch blocks have been updated to securely sanitize these messages using the existing
this.formatErrorForClient(error, correlationId)method, which prevents leakage of internal errors while passing through "safe" client-facing validation messages. A unique correlation ID is generated and logged alongside the raw error stack trace to allow safe internal debugging.β Verification: Updated
src/mcp/mcp-server-apps.test.tsto assert that themessagestring correctly incorporates the correlation UUID via regex and that validation errors correctly format. All unit and e2e tests were passed usingnpm run test.PR created automatically by Jules for task 3979447730811687819 started by @davidruzicka