dbcve.org
Netlify IpxApplication · Nuxtjs

CVE-2022-39239

MEDIUM · 5.4 CVSS v3.1 Published 2022-09-23
Fix available
A fix is available. Upgrade to 1.2.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
netlify-ipx is an on-Demand image optimization for Netlify using ipx. In versions prior to 1.2.3, an attacker can bypass the source image domain allowlist by sending specially crafted headers, 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. This problem has been fixed in version 1.2.3. As a workaround, cached content can be cleared by re-deploying the site.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

netlify-ipx versions before 1.2.3 allow attackers to bypass the source image domain allowlist by sending specially crafted headers, enabling the handler to load and return arbitrary images. Because responses are cached globally, these malicious images persist and are served to visitors without requiring the attack headers, enabling cache poisoning. XSS is achievable by requesting malicious SVG files with embedded scripts, which are served from the site domain.

MitigationUpgrade netlify-ipx to version 1.2.3 or later to patch the allowlist bypass. Clear cached content by re-deploying the site to remove any poisoned cache entries.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Netlify IpxApplication
Affected:< 1.2.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check netlify-ipx version
    Inspect your package.json dependencies or run 'npm list netlify-ipx' or 'yarn list netlify-ipx' to see the installed version
    Affected if The installed version is below 1.2.3 (e.g., 1.2.2, 1.2.1, etc.)
  2. Verify ipx endpoint exposure
    Check your Nuxt config (nuxt.config.js or nuxt.config.ts) for the netlify-ipx module configuration and confirm the /api/_ipx route is deployed and accessible on your live site
    Affected if The /api/_ipx endpoint is publicly accessible and netlify-ipx version is below 1.2.3
  3. Inspect for suspicious cached images
    Check the .netlify/functions and any custom cache directories for image files, particularly SVG files with unexpected content. Look for images from domains not in your allowlist.
    Affected if Cached images exist from domains not explicitly allowed in your ipx source domains configuration
  4. Test for allowlist bypass
    Send a request to /api/_ipx with a crafted Host header pointing to an unauthorized domain (e.g., 'Host: evil.com') and observe if the image loads
    Affected if The handler returns an image from a domain not in your configured allowlist, confirming the bypass works

You are affected if netlify-ipx version is below 1.2.3 and the ipx endpoint is exposed, as this allows arbitrary image loading, cache poisoning, and potential XSS via malicious SVG files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.2.3 or later
Fixed in 1.2.3
Interim mitigation

Upgrade netlify-ipx to version 1.2.3 or later to patch the allowlist bypass. Clear cached content by re-deploying the site to remove any poisoned cache entries.

Recommended fix High confidence

1.2.3

  1. Upgrade netlify-ipx to version 1.2.3 or later
  2. Re-deploy the site to clear any poisoned cache from the vulnerability

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Netlify Ipx Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-39239 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-39239 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data