ESLint version 0.6.2 represents a minor iteration over version 0.6.1 of this popular JavaScript linting tool, designed for identifying and enforcing coding standards. Both versions share the same core dependencies crucial for ESLint's functionality, including glob for file system navigation, chalk for console styling, escope for ECMAScript scope analysis, esprima for JavaScript parsing, js-yaml for YAML parsing, doctrine for JSDoc parsing, estraverse for AST traversal, optionator for option parsing, text-table for formatting text, cssauron-esprima for CSS selector matching, and strip-json-comments for removing comments from JSON.
The key difference lies within the devDependencies. Version 0.6.2 utilizes a specific version ^0.1.0 of eslint-tester, while version 0.6.1 utilizes the latest tag. This suggests updates or bug fixes in the testing framework used by ESLint developers. For developers using ESLint, this change likely translates to improved testing and potentially a more robust linting experience. The eslint-tester package helps ESLint developers ensure their rules function correctly, so a more recent and fixed version of this development dependency has a direct positive impact in the core package itself. In essence, version 0.6.2 offers a refinement in the testing infrastructure, contributing to the ongoing stability and reliability of ESLint as a code quality tool. Released nearly a week after 0.6.1, version 0.6.2 reflects the continuous effort to improve and maintain ESLint.
All the vulnerabilities related to the version 0.6.2 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.