ESLint version 0.4.1, a minor release following version 0.4.0, represents a refinement in this popular JavaScript linting tool. Both versions share core functionalities, leveraging Esprima for pattern checking and offering a suite of features for code analysis and style enforcement. The dependency structure remains consistent, with shared reliance on packages like glob, chalk, escope, and js-yaml for file system operations, terminal styling, scope analysis, and YAML parsing respectively. The development dependencies, crucial for testing and building the tool, are also identical, indicating a focus on stability and continued support.
However, the key distinction lies in the release dates. Version 0.4.1 was released on February 27, 2014, a little over two weeks after version 0.4.0, released on February 12, 2014. This suggests that version 0.4.1 likely incorporates bug fixes, minor enhancements, or updates to dependencies discovered after the initial 0.4.0 release. Since the core dependencies and dev dependencies are the same, developers can anticipate similar performance and capabilities across both versions. The upgrade from 0.4.0 to 0.4.1 should be seamless. Developers should upgrade to the latest minor version (0.4.1). Also, remember to check the changelog for detailed specific differences and improvements with this new version.
All the vulnerabilities related to the version 0.4.1 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.