fix: Add path traversal protection for schema file loading#380
Merged
Conversation
Add validation to prevent path traversal vulnerabilities when loading structured output schema files. The fix ensures that resolved file paths remain within the intended schemas directory by validating that the resolved path starts with the schemas directory path. This addresses a potential security issue where malicious input could potentially manipulate file paths through path traversal sequences. The fix adds checks in two locations: 1. In schemaPathFor() for schema files 2. In getMcpOutputSchema() for the common schema file Resolves: https://linear.app/getsentry/issue/VULN-1596 Resolves: https://linear.app/getsentry/issue/ENG-7560 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 210384d. Configure here.
commit: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

Summary
This PR fixes a path traversal vulnerability in the structured output schema loading code by adding validation to ensure that resolved file paths remain within the intended schemas directory.
Changes
schemaPathFor()function to validate schema file pathsgetMcpOutputSchema()for the common schema file pathSecurity Context
This addresses a Semgrep security finding where file paths were constructed from potentially untrusted data without sufficient validation. While the code already had regex validation for schema names and versions, it didn't prevent path traversal sequences like
../from escaping the intended directory.The fix uses
path.resolve()to normalize paths and validates that the resolved path stays within the schemas directory boundary.Testing
Existing tests in
src/core/__tests__/structured-output-schema.test.tsshould pass, validating that:References
🤖 Generated by fix-it-felix-sentry[bot]