chore(deps): update dependency @angular/platform-server to v20.3.19 [security] - autoclosed#33332
Closed
renovate[bot] wants to merge 1 commit into26_1from
Closed
chore(deps): update dependency @angular/platform-server to v20.3.19 [security] - autoclosed#33332renovate[bot] wants to merge 1 commit into26_1from
renovate[bot] wants to merge 1 commit into26_1from
Conversation
99cf76c to
99c9177
Compare
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.
This PR contains the following updates:
20.3.18→20.3.19Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
GitHub Vulnerability Alerts
GHSA-45q2-gjvg-7973
Impact
A Server-Side Request Forgery (SSRF) vulnerability exists in
@angular/platform-serverdue to improper handling of URLs during Server-Side Rendering (SSR).When an attacker sends a request such as
GET /\evil.com/ HTTP/1.1the server engine (Express, etc.) passes the URL string to Angular’s rendering functions.Because the URL parser normalizes the backslash to a forward slash for HTTP/HTTPS schemes, the internal state of the application is hijacked to believe the current origin is
evil.com. This misinterpretation tricks the application into treating the attacker’s domain as the local origin. Consequently, any relativeHttpClientrequests orPlatformLocation.hostnamereferences are redirected to the attacker controlled server, potentially exposing internal APIs or metadata services.Affected APIs:
renderModulerenderApplicationCommonEngine(from@angular/ssr)Non-Affected APIs:
AngularAppEngine(from@angular/ssr)AngularNodeAppEngine(from@angular/ssr)Attack Preconditions
req.url).HttpClientwith relative URLs or usesPlatformLocation.hostnameto build URLs.Patches
Workarounds
Developers should implement a middleware to sanitize the request URL before it reaches Angular. This involves stripping or normalizing leading slashes:
References
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/SA:NRelease Notes
angular/angular (@angular/platform-server)
v20.3.19Compare Source
platform-server
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.