CVE-2025-57752
ASP.NET Core Analyse et atténuation des vulnérabilités

Aperçu

Next.js, a React framework for building full-stack web applications, disclosed a cache key confusion vulnerability (CVE-2025-57752) affecting versions before 14.2.31 and from 15.0.0 to before 15.4.5. The vulnerability was discovered on August 29, 2025, and involves the Next.js Image Optimization API routes. When images returned from API routes vary based on request headers (such as Cookie or Authorization), these responses could be incorrectly cached and served to unauthorized users (NVD, GitHub Advisory).

Détails techniques

The vulnerability lies in the Next.js Image Optimizer's handling of images served from internal API routes. The root cause was identified in the fetchInternalImage function within packages/next/src/server/image-optimizer.ts. This function was forwarding the incoming request's headers to the internal API route, causing the route to generate user-specific images. However, the resulting optimized image was stored in the cache using a key that did not include the headers that influenced the image content. The vulnerability has been assigned a CVSS v3.1 base score of 6.2 (Moderate) with a vector string of CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (GitHub Advisory, Vercel Changelog).

Impact

The vulnerability could lead to unauthorized disclosure of user-specific or protected image content and cross-user leakage of conditional content via CDN or internal cache. This issue arises without user interaction and requires no elevated privileges, only a prior authorized request to populate the cache. It's worth noting that Vercel deployments were never impacted by this vulnerability (Vercel Changelog).

Atténuation et solutions de contournement

The issue has been fixed in Next.js versions 14.2.31 and 15.4.5. The resolution ensures that request headers aren't forwarded to the request that is proxied to the image endpoint, preventing the image endpoint from serving images that require authorization data and thus cannot be cached. All users are encouraged to upgrade if they use API routes to serve images that depend on request headers and have image optimization enabled (GitHub Advisory, Vercel Changelog).

Ressources additionnelles


SourceCe rapport a été généré à l’aide de l’IA

Apparenté ASP.NET Core Vulnérabilités:

Identifiant CVE

Sévérité

Score

Technologies

Nom du composant

Exploit CISA KEV

A corrigé

Date de publication

CVE-2025-55315CRITICAL9.9
  • C#C#
  • aspnetcore-runtime-dbg-8.0
NonOuiOct 14, 2025
CVE-2025-59144HIGH8.8
  • JavaScriptJavaScript
  • debug
NonOuiSep 15, 2025
CVE-2025-55247HIGH7.3
  • C#C#
  • dotnet9.0-debugsource
NonOuiOct 14, 2025
CVE-2025-57752MEDIUM6.2
  • ASP.NET CoreASP.NET Core
  • aspnetcore-targeting-pack-7.0
NonOuiAug 29, 2025
CVE-2025-55248MEDIUM5.7
  • C#C#
  • Microsoft.NetCore.App.Runtime.linux-musl-arm
NonOuiOct 14, 2025

Évaluation gratuite des vulnérabilités

Évaluez votre posture de sécurité dans le cloud

Évaluez vos pratiques de sécurité cloud dans 9 domaines de sécurité pour évaluer votre niveau de risque et identifier les failles dans vos défenses.

Demander une évaluation

Obtenez une démo personnalisée

Prêt(e) à voir Wiz en action ?

"La meilleure expérience utilisateur que j’ai jamais vue, offre une visibilité totale sur les workloads cloud."
David EstlickRSSI
"Wiz fournit une interface unique pour voir ce qui se passe dans nos environnements cloud."
Adam FletcherChef du service de sécurité
"Nous savons que si Wiz identifie quelque chose comme critique, c’est qu’il l’est réellement."
Greg PoniatowskiResponsable de la gestion des menaces et des vulnérabilités