ESLint version 0.4.3 represents a minor iteration in the early stages of the popular JavaScript linting tool, building upon the foundation of version 0.4.2. Both versions share identical core dependencies, including glob for file matching, chalk for terminal styling, escope for ECMAScript scope analysis, the core esprima parser, js-yaml for YAML parsing, doctrine for comment parsing, estraverse for AST traversal, optionator for option parsing, text-table for formatting text output, and strip-json-comments for handling JSON with comments. Likewise, the development dependencies used for testing and building, such as chai, mocha, sinon, browserify, istanbul and eslint-tester are consistent.
The crucial difference lies in the release date: version 0.4.3 was published on March 19, 2014, while version 0.4.2 was released on March 4, 2014. This two-week gap suggests that version 0.4.3 likely incorporates bug fixes, minor enhancements, or documentation updates discovered after the 0.4.2 release. While the specific nature of these changes isn't explicitly detailed in the metadata, users of ESLint 0.4.2 are encouraged to upgrade to 0.4.3 to benefit from these improvements and ensure they are using the most stable and up-to-date version within the 0.4.x series. Given the shared dependencies and the minor version bump, the upgrade is expected to be seamless and without significant compatibility issues. Developers should consult the changelog notes from the official repository to grasp full specifics of the differences if available.
All the vulnerabilities related to the version 0.4.3 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.