Vulnerabilities

2 via 4 paths

Dependencies

175

Source

GitHub

Commit

b357cae8

Find, fix and prevent vulnerabilities in your code.

Severity
  • 1
  • 1
Status
  • 2
  • 0
  • 0

high severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: next
  • Introduced through: @nhscc/backend-drive@1.3.1 and @nhscc/backend-qoverflow@1.2.1

Detailed paths

  • Introduced through: @nhscc/bdpa-cli@nhscc/bdpa-cli#b357cae83f707b194012aa768d18efb871cf226b @nhscc/backend-drive@1.3.1 next@15.5.14
  • Introduced through: @nhscc/bdpa-cli@nhscc/bdpa-cli#b357cae83f707b194012aa768d18efb871cf226b @nhscc/backend-qoverflow@1.2.1 next@15.5.14

Overview

next is a react framework.

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the Partial Prerendering resume endpoint when unauthenticated POST requests with the Next-Resume: 1 header are processed and attacker-controlled postponed state data is handled. An attacker can cause the server process to crash and exhaust system memory by sending large or highly compressed payloads that are buffered or decompressed without size limits.

Note:

This is only exploitable if the application is running with experimental.ppr: true or cacheComponents: true configured along with the NEXT_PRIVATE_MINIMAL_MODE=1 environment variable.

Remediation

Upgrade next to version 15.6.0-canary.61, 16.1.1-canary.16, 16.1.5 or higher.

References

medium severity
new

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: next
  • Introduced through: @nhscc/backend-drive@1.3.1 and @nhscc/backend-qoverflow@1.2.1

Detailed paths

  • Introduced through: @nhscc/bdpa-cli@nhscc/bdpa-cli#b357cae83f707b194012aa768d18efb871cf226b @nhscc/backend-drive@1.3.1 next@15.5.14
  • Introduced through: @nhscc/bdpa-cli@nhscc/bdpa-cli#b357cae83f707b194012aa768d18efb871cf226b @nhscc/backend-qoverflow@1.2.1 next@15.5.14

Overview

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.

Workaround

This vulnerability can be mitigated by periodically cleaning the .next/cache/images directory or by reducing the number of possible image variants through configuration of images.localPatterns, images.remotePatterns, and images.qualities.

Remediation

Upgrade next to version 16.1.7, 16.2.0-canary.54 or higher.

References