Astro has Full-Read SSRF in error rendering via Host: header injection

Astro is a web framework. Prior to version 9.5.4, Server-Side Rendered pages that return an error with a prerendered custom error page (eg. `404.astro` or `500.astro`) are vulnerable to SSRF. If the `Host:` header is changed to an attacker's server, it will be fetched on `/500.html` and they can redirect this to any internal URL to read the response body through the first request. An attacker who can access the application without `Host:` header validation (eg. through finding the origin IP behind a proxy, or just by default) can fetch their own server to redirect to any internal IP. With this they can fetch cloud metadata IPs and interact with services in the internal network or localhost. For this to be vulnerable, a common feature needs to be used, with direct access to the server (no proxies). Version 9.5.4 fixes the issue.

N/A

服务端请求伪造(SSRF)

Astro 代码问题漏洞

Astro是Astro开源的一个内容驱动网站的 web 框架。 Astro 9.5.4之前版本存在代码问题漏洞，该漏洞源于服务端渲染页面在处理错误时存在服务端请求伪造，可能导致攻击者访问内部网络服务。

N/A

N/A