Описание
Next.js versions from 16.3.0 to 16.3.7 warm use cache handlers using next/root-params and can leak their return value to pages with different root params. With Cache Components enabled (cacheComponents: true), a 'use cache' function that calls another 'use cache' function that reads a root param can be keyed incorrectly when the inner call is served from an existing entry: the enclosing function's cache key then omits that root param. The enclosing entry is written once and reused for all root param values, so a response for one root param value can serve content produced for a different value — whether the page is prerendered at build time or at runtime, or rendered dynamically. Shared cache headers let downstream caches redistribute the content further.
What values are leaked cannot be attacker controlled. Which value's content is served depends only on which invocation wrote the entry first.
This has been patched in 16.3.8.
A flaw was found in Next.js. This vulnerability may lead to information disclosure when nested caching features fail to properly include root parameters in their cache keys. An unauthenticated remote user can receive cached application responses intended for a different user or request context. This occurs because the application reuses a single cached entry across requests with differing parameters, potentially allowing intermediate caches to further redistribute the exposed data.
Отчет
This low impact information disclosure flaw affects the Next.js framework (npm package next), which is present as a dependency in Red Hat Enterprise Linux 7, 8, 9, and 10 (via the firefox and thunderbird components) and in Red Hat In-Vehicle OS. When the non-default Cache Components feature is enabled (cacheComponents: true), a 'use cache' function that calls another 'use cache' function that reads a root param can be keyed incorrectly when the inner call is served from an existing cache entry: the enclosing function's cache key then omits that root param. The cache entry is written once and reused for all root param values, so an unauthenticated remote user can receive cached application responses that were produced for a different root param value — whether the page is prerendered at build time or at runtime, or rendered dynamically — and shared cache headers allow downstream caches to redistribute the exposed content further. What values are leaked cannot be controlled by an attacker, and which value's content is served depends only on which invocation wrote the cache entry first. Red Hat's low severity rating (CVSS 3.7) differs from the upstream moderate rating (NIST 5.3, CVEORG 6.3) because exploitation requires the non-default cacheComponents configuration and a specific nested 'use cache' architecture, depends on invocation timing beyond the attacker's control, and results only in limited confidentiality impact. Because the impact is low, the fix for the affected Red Hat products is deferred, leaving a residual risk of limited cross-context exposure of cached content in applications that use the affected configuration.
Меры по смягчению последствий
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. The upstream project reports that there are no known workarounds and that applications should upgrade to the patched version, which is available as of Next.js 16.3.8.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Enterprise Linux 10 | firefox | Fix deferred | ||
| Red Hat Enterprise Linux 10 | thunderbird | Fix deferred | ||
| Red Hat Enterprise Linux 7 | firefox | Fix deferred | ||
| Red Hat Enterprise Linux 8 | firefox | Fix deferred | ||
| Red Hat Enterprise Linux 8 | thunderbird | Fix deferred | ||
| Red Hat Enterprise Linux 9 | firefox | Fix deferred | ||
| Red Hat Enterprise Linux 9 | thunderbird | Fix deferred | ||
| Red Hat Enterprise Linux AI (RHEL AI) 3 | rhelai3/bootc-cuda-rhel9 | Fix deferred | ||
| Red Hat Enterprise Linux AI (RHEL AI) 3 | rhelai3/bootc-gaudi-rhel9 | Fix deferred | ||
| Red Hat Enterprise Linux AI (RHEL AI) 3 | rhelai3/bootc-rocm-rhel9 | Fix deferred |
Показывать по
Дополнительная информация
Статус:
EPSS
3.7 Low
CVSS3
Связанные уязвимости
Next.js versions from 16.3.0 to 16.3.7 warm `use cache` handlers using `next/root-params` and can leak their return value to pages with different root params. With Cache Components enabled (cacheComponents: true), a 'use cache' function that calls another 'use cache' function that reads a root param can be keyed incorrectly when the inner call is served from an existing entry: the enclosing function's cache key then omits that root param. The enclosing entry is written once and reused for all root param values, so a response for one root param value can serve content produced for a different value — whether the page is prerendered at build time or at runtime, or rendered dynamically. Shared cache headers let downstream caches redistribute the content further. What values are leaked cannot be attacker controlled. Which value's content is served depends only on which invocation wrote the entry first. This has been patched in 16.3.8.
next.js cache leak across root param values in nested 'use cache' functions
EPSS
3.7 Low
CVSS3