Coffee-coverage provides Istanbul and JSCoverage-style instrumentation specifically tailored for CoffeeScript files, enabling developers to generate comprehensive code coverage reports for their CoffeeScript projects. Versions 0.6.0 and 0.5.4 share a common purpose and foundation, offering similar core functionalities. Both versions rely on key dependencies such as Chai for assertions, Lodash for utility functions, Pkginfo for package metadata, Argparse for command-line argument parsing, and CoffeeScript itself for processing CoffeeScript files. The development dependencies, including Mocha for testing, Sinon for mocking and stubbing, Istanbul for code coverage analysis, and Coveralls for coverage reporting, remain consistent across the two versions.
However, the key difference lies in the release date. Version 0.6.0 was released on May 19, 2015, while version 0.5.4 was released on May 6, 2015. This suggests that version 0.6.0 includes bug fixes, performance improvements, or incremental updates made after version 0.5.4. While the specific nature of these changes isn't explicitly detailed in the provided metadata, upgrading to version 0.6.0 is generally recommended, as it typically incorporates the latest refinements and enhancements. Developers using coffee-coverage can use it to integrate with their existing testing frameworks and CI/CD pipelines for continuous monitoring and improving code quality. To start using the library, one must install it as a dev dependency.
All the vulnerabilities related to the version 0.6.0 of the package
Command Injection in lodash
lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
Prototype Pollution in lodash
Versions of lodash before 4.17.11 are vulnerable to prototype pollution.
The vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow a malicious user to modify the prototype of Object via {constructor: {prototype: {...}}} causing the addition or modification of an existing property that will exist on all objects.
Update to version 4.17.11 or later.
Prototype Pollution in lodash
Versions of lodash before 4.17.5 are vulnerable to prototype pollution.
The vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow a malicious user to modify the prototype of Object via __proto__ causing the addition or modification of an existing property that will exist on all objects.
Update to version 4.17.5 or later.
Prototype Pollution in lodash
Versions of lodash before 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep allows a malicious user to modify the prototype of Object via {constructor: {prototype: {...}}} causing the addition or modification of an existing property that will exist on all objects.
Update to version 4.17.12 or later.
Prototype Pollution in lodash
Versions of lodash prior to 4.17.19 are vulnerable to Prototype Pollution. The functions pick, set, setWith, update, updateWith, and zipObjectDeep allow a malicious user to modify the prototype of Object if the property identifiers are user-supplied. Being affected by this issue requires manipulating objects based on user-provided property values or arrays.
This vulnerability causes the addition or modification of an existing property that will exist on all objects and may lead to Denial of Service or Code Execution under specific circumstances.
Arbitrary Code Execution in underscore
The package underscore from 1.13.0-0 and before 1.13.0-2, from 1.3.2 and before 1.12.1 are vulnerable to Arbitrary Code Execution via the template function, particularly when a variable property is passed as an argument as it is not sanitized.
Regular Expression Denial of Service in underscore.string
Versions of underscore.string prior to 3.3.5 are vulnerable to Regular Expression Denial of Service (ReDoS).
The function unescapeHTML is vulnerable to ReDoS due to an overly-broad regex. The slowdown is approximately 2s for 50,000 characters but grows exponentially with larger inputs.
Upgrade to version 3.3.5 or higher.
