Fix URI scheme validation for components from untrusted sources (IPC) #286620
+60
−3
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.
Description
The URI constructor skips validation when constructed from
UriComponentsobjects, assuming they're created by trusted internal code. This assumption breaks when components arrive via IPC, causing "[UriError]: Scheme contains illegal characters" to be thrown duringURI.revive()calls (17.3M hits, 3.4M users affected).Changes
_validateUri()when constructing fromUriComponentsto validate schemes from untrusted sources (IPC)-.+), and edge cases (empty scheme)The validation already exists and is simple (regex test). Empty schemes remain allowed for backward compatibility. No breaking changes - only malformed schemes from external sources are now rejected at construction time rather than causing obscure errors later.
Original prompt
💡 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.