ESLint version 0.5.0 represents an incremental update over its predecessor, version 0.4.5, bringing subtle but potentially impactful changes for JavaScript developers. The core functionality, described as an "Esprima-based pattern checker for JavaScript," remains consistent, emphasizing its role in code quality and style enforcement. Examining the dependencies, the most notable difference lies in the addition of cssauron-esprima in version 0.5.0, suggesting potential enhancements or new features related to CSS-in-JS or CSS-related linting rules. Also, optionator has been updated from ~0.1.1 to ~0.3.0. While both versions share a comprehensive suite of development dependencies for testing and building, the core libraries influencing code analysis and rules seem to be the primary focus of the update. Developers should investigate cssauron-esprima to understand the specific improvements it enables within ESLint's rule set.
Furthermore, the license information is presented slightly differently; version 0.4.5 has a dedicated "license" object with a URL and type, whereas version 0.5.0 simply specifies "MIT" directly. While functionally equivalent, this hints at a restructuring of the package metadata. Finally, the release dates clearly show that version 0.5.0 was released after version 0.4.5, solidifying it as the newer version. Developers keen on utilizing the latest features and bug fixes are encouraged to migrate to version 0.5.0, keeping a close eye on changes related to cssauron-esprima and optionator for any adjustments to their existing ESLint configurations.
All the vulnerabilities related to the version 0.5.0 of the package
Regular Expression Denial of Service in minimatch
Affected versions of minimatch are vulnerable to regular expression denial of service attacks when user input is passed into the pattern argument of minimatch(path, pattern).
var minimatch = require(“minimatch”);
// utility function for generating long strings
var genstr = function (len, chr) {
var result = “”;
for (i=0; i<=len; i++) {
result = result + chr;
}
return result;
}
var exploit = “[!” + genstr(1000000, “\\”) + “A”;
// minimatch exploit.
console.log(“starting minimatch”);
minimatch(“foo”, exploit);
console.log(“finishing minimatch”);
Update to version 3.0.2 or later.
minimatch ReDoS vulnerability
A vulnerability was found in the minimatch package. This flaw allows a Regular Expression Denial of Service (ReDoS) when calling the braceExpand function with specific arguments, resulting in a Denial of Service.
Denial of Service in js-yaml
Versions of js-yaml prior to 3.13.0 are vulnerable to Denial of Service. By parsing a carefully-crafted YAML file, the node process stalls and may exhaust system resources leading to a Denial of Service.
Upgrade to version 3.13.0.
Code Injection in js-yaml
Versions of js-yaml prior to 3.13.1 are vulnerable to Code Injection. The load() function may execute arbitrary code injected through a malicious YAML file. Objects that have toString as key, JavaScript code as value and are used as explicit mapping keys allow attackers to execute the supplied code through the load() function. The safeLoad() function is unaffected.
An example payload is
{ toString: !<tag:yaml.org,2002:js/function> 'function (){return Date.now()}' } : 1
which returns the object
{
"1553107949161": 1
}
Upgrade to version 3.13.1.
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.