GHSA-jvhm-gjrh-3h93HighCVSS 7.5

Nuxt allows DOS via cache poisoning with payload rendering response

Published
March 19, 2025
Last Modified
March 20, 2025

🔗 CVE IDs covered (1)

📋 Description

Summary

By sending a crafted HTTP request to a server behind an CDN, it is possible in some circumstances to poison the CDN cache and highly impacts the availability of a site.

It is possible to craft a request, such as https://mysite.com/?/_payload.json which will be rendered as JSON. If the CDN in front of a Nuxt site ignores the query string when determining whether to cache a route, then this JSON response could be served to future visitors to the site.

Impact

An attacker can perform this attack to a vulnerable site in order to make a site unavailable indefinitely. It is also possible in the case where the cache will be reset to make a small script to send a request each X seconds (=caching duration) so that the cache is permanently poisoned making the site completely unavailable.

Conclusion :

This is similar to a vulnerability in Next.js that resulted in CVE-2024-46982 (and see this article, in particular the "Internal URL parameter and pageProps" part, the latter being very similar to the one concerning us here.)

🎯 Affected products1

  • npm/nuxt:>= 3.0.0, < 3.16.0

🔗 References (3)