astro
Affected
- introduced
5.0.0-alpha.0, fixed5.13.2(semver)
Fixed versions
5.13.2
Fix
- Fixed version
5.13.2npm install [email protected]
Advisory
Also known as: CVE-2025-55303
Astro allows unauthorized third-party images in _image endpoint
Summary
In affected versions of astro, the image optimization endpoint in projects deployed with on-demand rendering allows images from unauthorized third-party domains to be served.
Details
On-demand rendered sites built with Astro include an /_image endpoint which returns optimized versions of images.
The /_image endpoint is restricted to processing local images bundled with the site and also supports remote images from domains the site developer has manually authorized (using the `image.domains` or `image.remotePatterns` options).
However, a bug in impacted versions of astro allows an attacker to bypass the third-party domain restrictions by using a protocol-relative URL as the image source, e.g. /_image?href=//example.com/image.png.
Proof of Concept
[email protected]).@astrojs/[email protected] — newer versions are not impacted): // astro.config.mjs
import { defineConfig } from 'astro/config';
import node from '@astrojs/node';
export default defineConfig({
adapter: node({ mode: 'standalone' }),
});
astro build.astro preview./_image?href=//placehold.co/600x400 to the preview URL, e.g. http://localhost:4321/_image?href=//placehold.co/600x400placehold.co origin.Impact
Allows a non-authorized third-party to create URLs on an impacted site’s origin that serve unauthorized image content.
In the case of SVG images, this could include the risk of cross-site scripting (XSS) if a user followed a link to a maliciously crafted SVG.
Medium Basis: The source's own band: MODERATE
5.0.0-alpha.0, fixed 5.13.2 (semver)5.13.2
5.13.2npm install [email protected]0, fixed 9.1.1 (semver)9.1.1
9.1.1npm install @astrojs/[email protected]0, fixed 4.16.19 (semver)4.16.19
4.16.19npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0