Vulnerabilities

3 via 3 paths

Dependencies

249

Source

npm

Find, fix and prevent vulnerabilities in your code.

Severity
  • 3
Status
  • 3
  • 0
  • 0

medium severity

Information Exposure

  • Vulnerable module: node-fetch
  • Introduced through: node-fetch@2.6.1

Detailed paths

  • Introduced through: next@12.0.5 node-fetch@2.6.1
    Remediation: Upgrade to next@12.0.9.

Overview

node-fetch is a light-weight module that brings window.fetch to node.js

Affected versions of this package are vulnerable to Information Exposure when fetching a remote url with Cookie, if it get a Location response header, it will follow that url and try to fetch that url with provided cookie. This can lead to forwarding secure headers to 3th party.

Remediation

Upgrade node-fetch to version 2.6.7, 3.1.1 or higher.

References

medium severity

User Interface (UI) Misrepresentation of Critical Information

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

Detailed paths

  • Introduced through: next@12.0.5
    Remediation: Upgrade to next@12.1.0.

Overview

next is a react framework.

Affected versions of this package are vulnerable to User Interface (UI) Misrepresentation of Critical Information due to improper CSP (content security policy).

Note: In order to be affected ALL of the following must be true:

  1. Next.js between version 10.0.0 and 12.0.10.

  2. The next.config.js file has images.domains array assigned.

  3. The image host assigned in images.domains allows user-provided SVG

Not affected: The next.config.js file has images.loader assigned to something other than "default".

Remediation

Upgrade next to version 12.1.0 or higher.

References

medium severity

Denial of Service (DoS)

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

Detailed paths

  • Introduced through: next@12.0.5
    Remediation: Upgrade to next@12.0.9.

Overview

next is a react framework.

Affected versions of this package are vulnerable to Denial of Service (DoS) when a static asset is requested with a locale prefix.

Note: This only affects users who are self-hosting their app and are using the internationalization functionality.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade next to version 12.0.9 or higher.

References