15.5.3
14 years ago
5 days ago
Known vulnerabilities in the next package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.
Fix for freeVulnerability | Vulnerable Version |
---|---|
next is a react framework. Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the Note: This is only exploitable if custom middleware logic is implemented in a self-hosted deployment. The project maintainers recommend using the documented How to fix Server-side Request Forgery (SSRF)? Upgrade | <14.2.32>=15.0.0 <15.4.2-canary.43>=15.4.3 <15.4.7 |
next is a react framework. Affected versions of this package are vulnerable to Use of Cache Containing Sensitive Information in the image optimization process, when responses from API routes vary based on request headers such as Note: Exploitation requires a prior authorized request to populate the cache. How to fix Use of Cache Containing Sensitive Information? Upgrade | <14.2.31>=15.0.0 <15.4.2-canary.19>=15.4.3 <15.4.5 |
next is a react framework. Affected versions of this package are vulnerable to Missing Source Correlation of Multiple Independent Data in Note: This is only exploitable if the application is configured to allow external image sources via the How to fix Missing Source Correlation of Multiple Independent Data? Upgrade | <14.2.31>=15.0.0 <15.4.2-canary.19>=15.4.3 <15.4.5 |
next is a react framework. Affected versions of this package are vulnerable to Race Condition in the Notes:
How to fix Race Condition? Upgrade | <14.2.24>=15.0.0 <15.1.6 |
next is a react framework. Affected versions of this package are vulnerable to Improper Authorization due to the improper handling of the How to fix Improper Authorization? Upgrade | >=11.1.4 <12.3.5>=13.0.0 <13.5.9>=14.0.0 <14.2.25>=15.0.0-rc.0 <15.2.3>=15.3.0-canary.0 <15.3.0-canary.12 |
next is a react framework. Affected versions of this package are vulnerable to Missing Authorization when using pathname-based checks in middleware for authorization decisions. If i18n configuration is not configured, an attacker can get unintended access to pages one level under the application's root directory. e.g. Note: Only self-hosted applications are vulnerable. The vulnerability has been fixed by Vercel on the server side. How to fix Missing Authorization? Upgrade | >=9.5.5 <13.5.8>=14.0.0 <14.2.15>=15.0.0-canary.0 <15.0.0-canary.177 |
next is a react framework. Affected versions of this package are vulnerable to Uncontrolled Recursion through the image optimization feature. An attacker can cause excessive CPU consumption by exploiting this vulnerability. How to fix Uncontrolled Recursion? Upgrade | >=10.0.0 <14.2.7>=15.0.0-canary.0 <15.0.0-canary.109 |
next is a react framework. Affected versions of this package are vulnerable to Resource Exhaustion via the How to fix Resource Exhaustion? Upgrade | <13.4.20-canary.13 |