Denial of Service (DoS) Affecting sails Open this link in a new tab package, versions >=0.11.0-rc6 <0.12.0-rc4
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.Test your applications
30 Jan 2017
3 Jun 2015
Introduced: 3 Jun 2015CWE-400 Open this link in a new tab
How to fix?
sails to version 0.12.0-rc4 or higher.
sails is API-driven framework for building realtime apps, using MVC conventions (based on Express and Socket.io).
Affected versions of the package are vulnerable to a Denial of Service (DoS) attack by sending an OPTIONS request for an undefined route, emitted on the socket.io REST interface. This causes
sails to become unresponsive.
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