Vulnerabilities

 8 via 8 paths

Dependencies

 131

Source

 GitHub

Commit

 e17523e3

Find, fix and prevent vulnerabilities in your code.

Test and protect my applications
Severity
  • 3
  • 4
  • 1
Status
  • 8
  • 0
  • 0

high severity

Server-side Request Forgery (SSRF)

  • Vulnerable module: next
  • Introduced through: next@12.3.7

Detailed paths

  • Introduced through: @opbi/ncm-preset-page@opbi/ncm-preset-page#e17523e3576250f73ccb70069167462794b448b6 › next@12.3.7
    Remediation: Upgrade to next@14.2.32.

Overview

next is a react framework.

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the resolve-routes. An attacker can access internal resources and potentially exfiltrate sensitive information by crafting requests containing user-controlled headers (e.g., Location) that are forwarded or interpreted without validation.

Note: This is only exploitable if custom middleware logic is implemented in a self-hosted deployment. The project maintainers recommend using the documented NextResponse.next({request}) to explicitly pass the request object.

Remediation

Upgrade next to version 14.2.32, 15.4.2-canary.43, 15.4.7 or higher.

References

Server-side Request Forgery (SSRF) vulnerability report

high severity

Missing Authorization

  • Vulnerable module: next
  • Introduced through: next@12.3.7

Detailed paths

  • Introduced through: @opbi/ncm-preset-page@opbi/ncm-preset-page#e17523e3576250f73ccb70069167462794b448b6 › next@12.3.7
    Remediation: Upgrade to next@13.5.8.

Overview

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. https://example.com/foo is accessible. https://example.com/ and https://example.com/foo/bar are not.

Note:

Only self-hosted applications are vulnerable. The vulnerability has been fixed by Vercel on the server side.

Remediation

Upgrade next to version 13.5.8, 14.2.15, 15.0.0-canary.177 or higher.

References

Missing Authorization vulnerability report

high severity

Uncontrolled Recursion

  • Vulnerable module: next
  • Introduced through: next@12.3.7

Detailed paths

  • Introduced through: @opbi/ncm-preset-page@opbi/ncm-preset-page#e17523e3576250f73ccb70069167462794b448b6 › next@12.3.7
    Remediation: Upgrade to next@14.2.7.

Overview

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.

Workaround

Ensure that the next.config.js file has either images.unoptimized, images.loader or images.loaderFile assigned.

Remediation

Upgrade next to version 14.2.7, 15.0.0-canary.109 or higher.

References

Uncontrolled Recursion vulnerability report

medium severity

Race Condition

  • Vulnerable module: next
  • Introduced through: next@12.3.7

Detailed paths

  • Introduced through: @opbi/ncm-preset-page@opbi/ncm-preset-page#e17523e3576250f73ccb70069167462794b448b6 › next@12.3.7
    Remediation: Upgrade to next@14.2.24.

Overview

next is a react framework.

Affected versions of this package are vulnerable to Race Condition in the Pages Router. An attacker can cause the server to serve incorrect pageProps data instead of the expected HTML content by exploiting a race condition between two requests, one containing the ?__nextDataRequest=1 query parameter and another with the x-now-route-matches header.

Notes:

  1. This is only exploitable if the CDN provider caches a 200 OK response even in the absence of explicit cache-control headers, enabling a poisoned response to persist and be served to subsequent users;

  2. No backend access or privileged escalation is possible through this vulnerability;

  3. Applications hosted on Vercel's platform are not affected by this issue, as the platform does not cache responses based solely on 200 OK status without explicit cache-control headers.

  4. This is a bypass of the fix for CVE-2024-46982

Workaround

This can be mitigated by stripping the x-now-route-matches header from all incoming requests at your CDN and setting cache-control: no-store for all responses under risk.

Remediation

Upgrade next to version 14.2.24, 15.1.6 or higher.

References

Race Condition vulnerability report

medium severity

Use of Cache Containing Sensitive Information

  • Vulnerable module: next
  • Introduced through: next@12.3.7

Detailed paths

  • Introduced through: @opbi/ncm-preset-page@opbi/ncm-preset-page#e17523e3576250f73ccb70069167462794b448b6 › next@12.3.7
    Remediation: Upgrade to next@14.2.31.

Overview

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 Cookie or Authorization. An attacker can gain unauthorized access to sensitive image data by exploiting cache key confusion, causing responses intended for authenticated users to be served to unauthorized users.

Note: Exploitation requires a prior authorized request to populate the cache.

Remediation

Upgrade next to version 14.2.31, 15.4.2-canary.19, 15.4.5 or higher.

References

Use of Cache Containing Sensitive Information vulnerability report

medium severity

Resource Exhaustion

  • Vulnerable module: next
  • Introduced through: next@12.3.7

Detailed paths

  • Introduced through: @opbi/ncm-preset-page@opbi/ncm-preset-page#e17523e3576250f73ccb70069167462794b448b6 › next@12.3.7
    Remediation: Upgrade to next@13.5.0.

Overview

next is a react framework.

Affected versions of this package are vulnerable to Resource Exhaustion via the cache-control header. An attacker can cause a denial of service to all users requesting the same URL via a CDN by caching empty prefetch responses.

Remediation

Upgrade next to version 13.4.20-canary.13 or higher.

References

Resource Exhaustion vulnerability report

medium severity

Improper Input Validation

  • Vulnerable module: postcss
  • Introduced through: next@12.3.7

Detailed paths

  • Introduced through: @opbi/ncm-preset-page@opbi/ncm-preset-page#e17523e3576250f73ccb70069167462794b448b6 › next@12.3.7 › postcss@8.4.14
    Remediation: Upgrade to next@13.5.4.

Overview

postcss is a PostCSS is a tool for transforming styles with JS plugins.

Affected versions of this package are vulnerable to Improper Input Validation when parsing external Cascading Style Sheets (CSS) with linters using PostCSS. An attacker can cause discrepancies by injecting malicious CSS rules, such as @font-face{ font:(\r/*);}. This vulnerability is because of an insecure regular expression usage in the RE_BAD_BRACKET variable.

Remediation

Upgrade postcss to version 8.4.31 or higher.

References

Improper Input Validation vulnerability report

low severity

Missing Source Correlation of Multiple Independent Data

  • Vulnerable module: next
  • Introduced through: next@12.3.7

Detailed paths

  • Introduced through: @opbi/ncm-preset-page@opbi/ncm-preset-page#e17523e3576250f73ccb70069167462794b448b6 › next@12.3.7
    Remediation: Upgrade to next@14.2.31.

Overview

next is a react framework.

Affected versions of this package are vulnerable to Missing Source Correlation of Multiple Independent Data in image-optimizer. An attacker can cause arbitrary files to be downloaded with attacker-controlled content and filenames by supplying malicious external image sources.

Note: This is only exploitable if the application is configured to allow external image sources via the images.domains or images.remotePatterns configuration.

Remediation

Upgrade next to version 14.2.31, 15.4.2-canary.19, 15.4.5 or higher.

References

Missing Source Correlation of Multiple Independent Data vulnerability report