|2 via 2 paths|
Find, fix and prevent vulnerabilities in your code.
- Vulnerable module: next
- Introduced through: email@example.com
Introduced through: firstname.lastname@example.orgRemediation: Upgrade to email@example.com.
next is a react framwork.
Affected versions of this package are vulnerable to Denial of Service (DoS) due to mishandling of invalid URLs. Note: This vulnerability is only possible for Node.js versions of 15.0.0 and above. Also, deployments on Vercel (vercel.com) are not affected along with similar environments where invalid requests are filtered before reaching Next.js.
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
next to version 12.0.5, 11.1.3 or higher.
- Vulnerable module: node-fetch
- Introduced through: firstname.lastname@example.org
Introduced through: email@example.com › firstname.lastname@example.orgRemediation: Upgrade to email@example.com.
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.
node-fetch to version 2.6.7, 3.1.1 or higher.