CVE-2017-20162: vercel ms index.js parse redos
A vulnerability, which was classified as problematic, has been found in vercel ms up to 1.x. This issue affects the function parse of the file index.js. The manipulation of the argument str leads to inefficient regular expression complexity. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 2.0.0 is able to address this issue. The name of the patch is caae2988ba2a37765d055c4eee63d383320ee662. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-217451.
Other sources
A vulnerability, which was classified as problematic, has been found in vercel ms up to 1.x. This issue affects the function parse of the file index.js. The manipulation of the argument str leads to inefficient regular expression complexity. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 2.0.0 is able to address this issue. The patch is named caae2988ba2a37765d055c4eee63d383320ee662. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-217451.
Vercel ms is vulnerable to a denial of service, caused by a regular expression denial of service (ReDoS) flaw in the function parse of the file index.js. By sending a specially-crafted regex input, a remote authenticated attacker could exploit this vulnerability to cause a denial of service condition.
— IBM
Affected Software
Remediation
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2017-20162?
The severity of CVE-2017-20162 is medium with a CVSS score of 5.3.
What is the affected software for CVE-2017-20162?
The affected software for CVE-2017-20162 is vercel ms up to version 1.x and node.js up to version 2.0.0.
How can the vulnerability in CVE-2017-20162 be exploited?
The vulnerability in CVE-2017-20162 can be exploited remotely by manipulating the argument 'str' to cause inefficient regular expression complexity.
What is the remedy for CVE-2017-20162?
The remedy for CVE-2017-20162 is to upgrade to version 2.0.0 of vercel ms.
Where can I find more information about CVE-2017-20162?
More information about CVE-2017-20162 can be found at the following references: [1](https://nvd.nist.gov/vuln/detail/CVE-2017-20162), [2](https://github.com/vercel/ms/pull/89), [3](https://github.com/vercel/ms/commit/caae2988ba2a37765d055c4eee63d383320ee662).