[Aikido] Fix security issue in astro via minor version upgrade from 5.12.9 to 5.16.3 in frontend #88
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.
Upgrading astro to address vulnerabilities.
10 CVEs resolved by this upgrade
This PR will resolve the following CVEs:
/%2561dmin) to access routes that should be behind authentication. The patch fixes this by decoding pathnames and rejecting requests that...x-forwarded-protoandx-forwarded-portare insecurely used, without sanitization, to build the URL. This has several consequences, the most important of which are: midd...X-Forwarded-Hostin output when usingAstro.urlwithout any validation. It is common for web servers such as nginx to route requests via theHostheader, and forward on other request headers. As such as malicious re...trailingSlashconfiguration option is used. An attacker can inject arbitrary JavaScript code that executes...X-Forwarded-Host,X-Forwarded-Proto, andX-Forwarded-Portheaders. Attackers could inject or manipulate these headers to bypass domain restrictions, influence rout...