fix(@angular/ssr): prevent malicious URL from overriding host #31474
Conversation
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
alan-agius4
added
action: review
A request with a specially crafted URL starting with a double slash (e.g., `//example.com`) could cause the server-side rendering logic to interpret the request as being for a different host. This is due to the behavior of the `URL` constructor when a protocol-relative URL is passed as the first argument. This vulnerability could be exploited to make the server execute requests to a malicious domain when relative paths are used within the application (e.g., via `HttpClient`), potentially leading to content injection or other security risks. The fix ensures that the request URL is always constructed as a full URL string, including the protocol and host, before being passed to the `URL` constructor. This prevents the host from being overridden by the path. Closes angular#31464
jkrems
approved these changes
Oct 15, 2025
jkrems
added
action: merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
A request with a specially crafted URL starting with a double slash (e.g.,
//example.com) could cause the server-side rendering logic to interpret the request as being for a different host. This is due to the behavior of theURLconstructor when a protocol-relative URL is passed as the first argument.This vulnerability could be exploited to make the server execute requests to a malicious domain when relative paths are used within the application (e.g., via
HttpClient), potentially leading to content injection or other security risks.The fix ensures that the request URL is always constructed as a full URL string, including the protocol and host, before being passed to the
URLconstructor. This prevents the host from being overridden by the path.Closes #31464