Body-parser version 1.15.2 is a minor update to the popular Node.js middleware for parsing incoming request bodies. Released on June 20, 2016, it builds upon the previous stable version, 1.15.1, offering subtle improvements and bug fixes. Developers familiar with body-parser will find the core functionality unchanged, providing a seamless transition. Key dependency updates include a newer version of 'qs' (6.2.0 vs 6.1.0) for robust query string parsing and 'bytes' (2.4.0 vs 2.3.0) for handling byte units. Type-is has also been updated from ~1.6.12 to ~1.6.13. Raw-body sees a bump from ~2.1.6 to ~2.1.7 and http-errors moves from ~1.4.0 to ~1.5.0, potentially addressing edge cases or security vulnerabilities. A minor update to content-type from ~1.0.1 to ~1.0.2 might also be observed.
Significantly, version 1.15.2 introduces several new development dependencies, including 'eslint', 'eslint-plugin-promise', 'eslint-config-standard', and 'eslint-plugin-standard', suggesting an increased focus on code quality and adherence to coding standards. This results in overall improved code maintainability and reduced potential for bugs, as well as allowing for a new set of automated linting. The addition of Istanbul, as well as Mocha and Supertest, remain constant with the prior version, indicating consistent testing and code coverage practices. Developers looking for a reliable and well-maintained solution for parsing JSON, URL-encoded, and other request bodies will appreciate the incremental improvements in stability and code quality offered by version 1.15.2.
All the vulnerabilities related to the version 1.15.2 of the package
body-parser vulnerable to denial of service when url encoding is enabled
body-parser <1.20.3 is vulnerable to denial of service when url encoding is enabled. A malicious actor using a specially crafted payload could flood the server with a large number of requests, resulting in denial of service.
this issue is patched in 1.20.3
Prototype Pollution Protection Bypass in qs
Affected version of qs are vulnerable to Prototype Pollution because it is possible to bypass the protection. The qs.parse function fails to properly prevent an object's prototype to be altered when parsing arbitrary input. Input containing [ or ] may bypass the prototype pollution protection and alter the Object prototype. This allows attackers to override properties that will exist in all objects, which may lead to Denial of Service or Remote Code Execution in specific circumstances.
Upgrade to 6.0.4, 6.1.2, 6.2.3, 6.3.2 or later.
qs vulnerable to Prototype Pollution
qs before 6.10.3 allows attackers to cause a Node process hang because an __ proto__ key can be used. In many typical web framework use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[__proto__]=b&a[__proto__]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4.
debug Inefficient Regular Expression Complexity vulnerability
A vulnerability classified as problematic has been found in debug-js debug up to 3.0.x. This affects the function useColors of the file src/node.js. The manipulation of the argument str leads to inefficient regular expression complexity. Upgrading to version 3.1.0 is able to address this issue. The name of the patch is c38a0166c266a679c8de012d4eaccec3f944e685. It is recommended to upgrade the affected component. The identifier VDB-217665 was assigned to this vulnerability. The patch has been backported to the 2.6.x branch in version 2.6.9.
Regular Expression Denial of Service in debug
Affected versions of debug are vulnerable to regular expression denial of service when untrusted user input is passed into the o formatter.
As it takes 50,000 characters to block the event loop for 2 seconds, this issue is a low severity issue.
This was later re-introduced in version v3.2.0, and then repatched in versions 3.2.7 and 4.3.1.
Version 2.x.x: Update to version 2.6.9 or later. Version 3.1.x: Update to version 3.1.0 or later. Version 3.2.x: Update to version 3.2.7 or later. Version 4.x.x: Update to version 4.3.1 or later.
Vercel ms Inefficient Regular Expression Complexity vulnerability
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.
