Denial of Service (DoS) Affecting decode-uri-component package, versions <0.2.2
Threat Intelligence
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- Snyk ID SNYK-JS-DECODEURICOMPONENT-3149970
- published 28 Nov 2022
- disclosed 28 Nov 2022
- credit KatsuragiCSL
Introduced: 28 Nov 2022
CVE-2022-38900 Open this link in a new tabHow to fix?
Upgrade decode-uri-component to version 0.2.2 or higher.
Overview
Affected versions of this package are vulnerable to Denial of Service (DoS) due to improper input validation, when the hash string # kun%ea%ba%5a%ba is being parsed by decodeUriComponent.
PoC
const decodeUriComponent = require('decode-uri-component');
var x = decodeUriComponent('%ea%ba%5a%ba');
console.log(x);
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
wspackage