Body-parser version 1.5.2 is a minor update from 1.5.1 in this popular Node.js middleware for parsing request bodies. Both versions, crucial for handling incoming data in Express applications, provide robust tools for processing various content types. Developers using either version can expect similar core functionality for parsing JSON, URL-encoded, and raw request bodies, streamlining data extraction in their applications. Key dependencies like qs, bytes, type-is, raw-body, iconv-lite, and media-typer remain consistent, ensuring compatibility and reliability. However, the update includes a subtle yet potentially important change: the depd dependency, responsible for handling deprecation warnings, is updated from version 0.4.3 to 0.4.4. This likely addresses minor bug fixes or improved deprecation handling within the depd module itself, offering a slightly refined developer experience. Testing frameworks like mocha, should, istanbul, and supertest are unchanged, suggesting that the core functionality remains unaltered. The release date difference of one day further highlights the incremental nature of this update, implying that version 1.5.2 primarily focuses on internal improvements and dependency maintenance rather than introducing significant new features. Developers should consider upgrading to leverage the latest dependency versions.
All the vulnerabilities related to the version 1.5.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
Denial-of-Service Extended Event Loop Blocking in qs
Versions prior to 1.0.0 of qs are affected by a denial of service vulnerability that results from excessive recursion in parsing a deeply nested JSON string.
Update to version 1.0.0 or later
Denial-of-Service Memory Exhaustion in qs
Versions prior to 1.0 of qs are affected by a denial of service condition. This condition is triggered by parsing a crafted string that deserializes into very large sparse arrays, resulting in the process running out of memory and eventually crashing.
Update to version 1.0.0 or later.
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.
