Advisory

GHSA-9jjv-524m-jm98

Also known as: CVE-2022-39239

Summary

@netlify/ipx vulnerable to Full Response SSRF and Stored XSS via Cache Poisoning and Improper Host Validation

Details

Impact

By sending specially crafted headers an attacker can bypass the source image domain allowlist, causing the handler to load and return arbitrary images. Because the response is cached globally, this image will then be served to visitors without requiring those headers to be set. XSS can be achieved by requesting a malicious SVG with embedded scripts, which would then be served from the site domain. Note that this does not apply to images loaded in <img> tags, as scripts do not execute in this context. The image URL can be set in the header independently of the request URL, meaning any site images that have not previously been cached can have their cache poisoned.

Patches
This problem has been fixed in version 1.2.3

Workarounds

The problem is no longer exploitable on Netlify as the CDN now sanitizes the relevant header. Cached content can be cleared by re-deploying the site.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2022-09-21 21:42 UTC
Modified
2023-11-08 04:10 UTC

Affected packages and fixes

@netlify/ipx

npm · All systems

Affected

  • introduced 0, fixed 1.2.3 (semver)

Fixed versions

1.2.3

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences