Mocha version 3.5.0 introduces subtle but potentially important updates compared to version 3.4.2, primarily impacting the development dependencies used for testing and building the library itself. One key change is the upgrade of the 'debug' dependency from version 2.6.0 to 2.6.8, suggesting potential bug fixes or performance improvements in the debugging capabilities. A notable change is the move of @coderbyheart/karma-sauce-launcher from a direct github repository reference to a git URL with a specific commit hash, ensuring more predictable and stable builds by locking the dependency to a precise state, while the previous version just referenced the repo. Several development dependencies have been updated, most notably should has been downgraded from version 11.1.1 to 9.0.2, a change that could potentially impact assertion behavior for contributors or those extending Mocha's functionalities. Another significant change is the update of readable-stream to version 2.2.11, which might impact how streams are handled during testing. It's worth noting the updated release date, indicating that version 3.5.0 was released in July 2017, offering developers a refresh of the testing framework with potential refinements and fixes accumulated since the previous release in May 2017. Developers relying on specific versions of any of these underlying development tools should carefully evaluate the potential impact of these updates. While these changes primarily affect the development environment, they contribute to the overall stability and maintainability of the Mocha library, indirectly benefiting end-users.
All the vulnerabilities related to the version 3.5.0 of the package
Regular Expression Denial of Service (ReDoS)
A vulnerability was found in diff before v3.5.0, the affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks.
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.
Growl before 1.10.0 vulnerable to Command Injection
Affected versions of growl do not properly sanitize input prior to passing it into a shell command, allowing for arbitrary command execution.
Update to version 1.10.0 or later.
Prototype Pollution in minimist
Affected versions of minimist are vulnerable to prototype pollution. Arguments are not properly sanitized, allowing an attacker to modify the prototype of Object, causing the addition or modification of an existing property that will exist on all objects.
Parsing the argument --__proto__.y=Polluted adds a y property with value Polluted to all objects. The argument --__proto__=Polluted raises and uncaught error and crashes the application.
This is exploitable if attackers have control over the arguments being passed to minimist.
Upgrade to versions 0.2.1, 1.2.3 or later.
Prototype Pollution in minimist
Minimist prior to 1.2.6 and 0.2.4 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).
