Описание
@astrojs/node: Backslash-prefixed paths not recognized as internal by trailing-slash redirect
Impact
With trailingSlash: 'always' configured, the @astrojs/node standalone server's static file handler appends a trailing slash to request paths and issues a 301 redirect. Paths beginning with /\ (slash-backslash) were not recognized as internal paths, so the handler would echo the raw path back in the Location header. Because browsers treat \ as / per the WHATWG URL specification, the resulting redirect could resolve to an external host.
Preconditions:
trailingSlash: 'always'must be set (non-default; the default is'ignore')- The request path must not have a file extension in its final segment
- An attacker must deliver the crafted link to a user
Patches
Fixed by treating backslash-prefixed paths the same as //-prefixed paths in isInternalPath(), so they are no longer rewritten with a trailing slash.
Workarounds
Use the default trailingSlash: 'ignore' setting, which does not issue trailing-slash redirects in the static file handler.
References
Ссылки
- https://github.com/withastro/astro/security/advisories/GHSA-r557-wffq-wvrc
- https://nvd.nist.gov/vuln/detail/CVE-2026-59730
- https://github.com/withastro/astro/pull/17252
- https://github.com/withastro/astro/commit/eb6f97e391ee587747e37609c255c7cd4b9cce3c
- https://github.com/withastro/astro/releases/tag/@astrojs/node@11.0.2
Пакеты
@astrojs/node
>= 8.1.0, < 11.0.2
11.0.2
Связанные уязвимости
Astro is a web framework for content-driven websites. In versions 8.1.0 through 11.0.1, when trailingSlash: 'always' is configured, the @astrojs/node standalone server's static file handler appends a trailing slash to request paths and issues a 301 redirect. Paths beginning with /\ (slash-backslash) were not recognized as internal paths, so the handler would echo the raw path back in the Location header. Because browsers treat \ as / per the WHATWG URL specification, the resulting redirect could resolve to an external host. Preconditions for exploitation: trailingSlash: 'always' must be set (non-default; the default is 'ignore'), the request path must not have a file extension in its final segment, and an attacker must deliver the crafted link to a user. This issue has been fixed in version 11.0.2.