Coffee-coverage is a valuable tool for developers seeking to integrate code coverage analysis into their CoffeeScript projects, offering Istanbul and JSCoverage-style instrumentation. Comparing versions 0.5.4 and 0.5.3, the core functionality remains consistent, indicated by identical dependency specifications: chai, lodash, pkginfo, argparse, and coffee-script. Similarly, development dependencies like mocha, sinon, istanbul, and coveralls stay unchanged between versions, suggesting a stable testing and coverage analysis environment across both releases. The repository information and author details also remain the same, solidifying the project's continuous maintenance and provenance.
The key differentiator lies in the release date. Version 0.5.4 was published on May 6th, 2015, a single day after version 0.5.3, released on May 5th, 2015. This suggests that version 0.5.4 is likely a patch release addressing minor bugs, documentation improvements, or other non-breaking changes identified shortly after the 0.5.3 release. For developers already using coffee-coverage, upgrading from 0.5.3 to 0.5.4 is recommended to ensure access to the latest refinements. New users should directly adopt version 0.5.4 for the most up-to-date and potentially stable experience analyzing CoffeeScript code coverage. The package's availability through npm with easily accessible tarball links makes integration into existing workflows straightforward.
All the vulnerabilities related to the version 0.5.4 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.
