ESLint version 0.2.0 introduces a minor version bump over 0.1.4, signaling small but potentially important changes. Both versions share the same core dependencies: escope (version 1.0.0), esprima, optimist, and estraverse (version ~1.3.0), suggesting the fundamental JavaScript parsing and analysis capabilities remain consistent. Similarly, the developer dependencies, including testing frameworks like chai, mocha, and sinon, and utilities like jshint, shelljs, istanbul, jsonlint, and commonjs-everywhere, are identical. This indicates a continuous commitment to testing, code quality, and tooling support.
The most noticeable difference is the release date. Version 0.2.0 was released on January 1, 2014, while 0.1.4 was released on December 6, 2013, roughly a month earlier. While the core dependencies appear locked, developers should investigate the changelog or release notes (not provided here) for 0.2.0 to understand bug fixes, new rule additions, or modifications to existing rules that might impact code linting. Even minor version changes can introduce breaking changes or enforce stricter code style guidelines, so a careful review is crucial before upgrading. It's advisable to consult the official ESLint documentation and community resources for detailed information regarding version-specific updates and best practices. This approach will ensure a smooth transition and leverage the latest improvements offered by ESLint.
All the vulnerabilities related to the version 0.2.0 of the package
Prototype Pollution in minimist
Affected versions of minimist are vulnerable to prototype pollution. Arguments are not properly sanitized, allowing an attacker to modify the prototype of Object, causing the addition or modification of an existing property that will exist on all objects.
Parsing the argument --__proto__.y=Polluted adds a y property with value Polluted to all objects. The argument --__proto__=Polluted raises and uncaught error and crashes the application.
This is exploitable if attackers have control over the arguments being passed to minimist.
Upgrade to versions 0.2.1, 1.2.3 or later.
Prototype Pollution in minimist
Minimist prior to 1.2.6 and 0.2.4 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).
