16.2.7
14 years ago
6 days ago
Known vulnerabilities in the next package. This does not include vulnerabilities belonging to this package’s dependencies.
Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.
Fix for free| Vulnerability | Vulnerable Version |
|---|---|
next is a react framework. Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via the CSP nonce headers. An attacker can inject malicious scripts into cached HTML responses by supplying malformed nonce values, which may then be executed in the browsers of subsequent visitors. This is possible when applications are deployed behind shared caches and rely on request-derived nonce values. How to fix Cross-site Scripting (XSS)? Upgrade | >=13.4.13-canary.0 <15.5.16>=16.0.0-beta.0 <16.2.5 |
next is a react framework. Affected versions of this package are vulnerable to Incorrect Authorization in the How to fix Incorrect Authorization? Upgrade | >=12.2.0 <15.5.16>=16.0.0-beta.0 <16.2.5 |
next is a react framework. Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via crafted WebSocket upgrade requests. An attacker can access internal or external resources by sending specially crafted requests with absolute-url that cause the server to proxy connections to arbitrary destinations, potentially exposing sensitive internal services or cloud metadata endpoints. How to fix Server-side Request Forgery (SSRF)? Upgrade | >=13.4.13-canary.0 <15.5.16>=16.0.0-beta.0 <16.2.5 |
next is a react framework. Affected versions of this package are vulnerable to Cross-site Scripting (XSS) in the How to fix Cross-site Scripting (XSS)? Upgrade | >=13.0.0 <15.5.16>=16.0.0-beta.0 <16.2.5 |
next is a react framework. Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the Image Optimization API when handling requests to the Note: This is only exploitable if the default image loader is used and the How to fix Allocation of Resources Without Limits or Throttling? Upgrade | >=10.0.0 <15.5.16>=16.0.0-beta.0 <16.2.5 |
next is a react framework. Affected versions of this package are vulnerable to Use of Weak Hash via collisions in the How to fix Use of Weak Hash? Upgrade | >=13.4.6-canary.0 <15.5.16>=16.0.0-beta.0 <16.2.5 |
next is a react framework. Affected versions of this package are vulnerable to Interpretation Conflict via improper handling of shared cache entries for React Server Component responses. An attacker can cause unintended component payloads to be served to other users by manipulating shared cache behavior through crafted requests. How to fix Interpretation Conflict? Upgrade | >=14.2.0-canary.0 <15.5.16>=16.0.0-beta.0 <16.2.5 |
next is a react framework. Affected versions of this package are vulnerable to Acceptance of Extraneous Untrusted Data With Trusted Data through the improper handling of the How to fix Acceptance of Extraneous Untrusted Data With Trusted Data? Upgrade | >=12.2.0 <15.5.16>=16.0.0-beta.0 <16.2.5 |
next is a react framework. Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via server function endpoints. An attacker can cause out-of-memory exceptions or induce excessive CPU usage by sending malicious Note: Only React apps that use React Server Components are vulnerable. How to fix Allocation of Resources Without Limits or Throttling? Upgrade | >=13.0.0 <15.5.16>=16.0.0-beta.0 <16.2.5 |
next is a react framework. Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the How to fix Allocation of Resources Without Limits or Throttling? Upgrade | >=13.0.0 <15.5.15>=15.6.0-canary.0 <16.2.3 |
next is a react framework. Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in the decoding reply functions of React Flight protocol. An attacker can cause server crashes, out-of-memory exceptions, or excessive CPU usage by sending specially crafted HTTP requests to Server Function endpoints. Notes:
How to fix Allocation of Resources Without Limits or Throttling? Upgrade | >=13.0.0 <15.0.8>=15.1.0 <15.1.12>=15.2.0-canary.0 <15.2.9>=15.3.0-canary.0 <15.3.9>=15.4.0-canary.0 <15.4.11>=15.5.0 <15.5.10>=15.6.0-canary.0 <15.6.0-canary.61>=16.0.0-canary.0 <16.0.11>=16.1.0-canary.0 <16.1.5>=16.2.0-canary.0 <16.2.0-canary.9 |
next is a react framework. Affected versions of this package are vulnerable to HTTP Request Smuggling during the rewrite of the proxy traffic to an external backend. An attacker can access unintended backend routes by sending crafted How to fix HTTP Request Smuggling? Upgrade | >=9.5.0 <15.5.13>=16.0.0-beta.0 <16.1.7>=16.2.0-canary.0 <16.2.0-canary.102 |
next is a react framework. Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling due to the lack of an upper bound on the disk cache used by the image optimization. An attacker can exhaust disk storage by generating a large number of unique image optimization variants, leading to service disruption. How to fix Allocation of Resources Without Limits or Throttling? Upgrade | >=10.0.0 <16.1.7>=16.2.0-canary.0 <16.2.0-canary.54 |
next is a react framework. Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the Note: This is only exploitable if How to fix Allocation of Resources Without Limits or Throttling? Upgrade | >=10.0.0 <15.5.10>=16.0.0-beta.0 <16.1.1-canary.15>=16.1.1 <16.1.5 |