Skip to content

πŸ›‘οΈ Sentinel: [CRITICAL] Fix Internal Error Leakage via API Responses in MCP Server#254

Open
davidruzicka wants to merge 1 commit into
mainfrom
sentinel-fix-internal-error-leakage-mcp-server-3979447730811687819
Open

πŸ›‘οΈ Sentinel: [CRITICAL] Fix Internal Error Leakage via API Responses in MCP Server#254
davidruzicka wants to merge 1 commit into
mainfrom
sentinel-fix-internal-error-leakage-mcp-server-3979447730811687819

Conversation

@davidruzicka
Copy link
Copy Markdown
Owner

🚨 Severity: CRITICAL
πŸ’‘ Vulnerability: The MCP server JSON-RPC handlers for prompts/get, resources/read, and completion/complete were catching raw runtime and logic exceptions and leaking the un-sanitized error message string directly to the client in the error.message field 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.ts to assert that the message string correctly incorporates the correlation UUID via regex and that validation errors correctly format. All unit and e2e tests were passed using npm run test.


PR created automatically by Jules for task 3979447730811687819 started by @davidruzicka

…in MCP Server

Co-authored-by: davidruzicka <14172985+davidruzicka@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

πŸ‘‹ 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.

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 18, 2026

Codecov Report

βœ… All modified and coverable lines are covered by tests.
βœ… All tests successful. No failed tests found.

πŸ“’ Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant