Clarify path validation logic in safeWorkspaceResolve #100
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.
Addressed review feedback questioning the necessity of path validation when
absPathis already absolute.Context
The
safeWorkspaceResolvefunction validates that resolved paths remain within/workspace. Reviewer questioned why validation is needed for absolute paths.Clarification Provided
No code changes required. The validation serves two security purposes:
/etc/passwdresolves to an absolute path outside/workspacefs.realpathSync()resolves symlink targets which may point outside the workspaceThe check
!realPath.startsWith(workspaceRoot + path.sep)validates the final resolved path after both absolute path resolution and symlink dereferencing.💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.