🛡️ Sentinel: Fix CSRF vulnerability by enforcing Origin validation on localhost #41
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change removes a security vulnerability where
Originheader validation was skipped for requests tolocalhostor127.0.0.1. This behavior could allow malicious websites to perform Cross-Site Request Forgery (CSRF) attacks against a locally running MCP server.Changes:
src/http-transport.tsto remove the early return that bypassed Origin checks for localhost.src/http-transport.test.tsto include a test case verifying that requests with malicious origins are rejected (403 Forbidden) even when the Host is localhost..jules/sentinel.mdwith a journal entry documenting this vulnerability and the fix.PR created automatically by Jules for task 6786025401319321649 started by @davidruzicka