ESLint version 0.1.3 arrives shortly after 0.1.2, offering a subtle but potentially significant update for JavaScript developers seeking a reliable linting tool. Both versions leverage Esprima for parsing, ensuring robust JavaScript analysis. Core dependencies like escope, esprima, optimist, and estraverse remain consistent, indicating stability in the fundamental analysis engine.
The key difference lies in the development dependencies. Version 0.1.3 replaces grunt-vows-runner (used in 0.1.2) with grunt-istanbul-coverage and it adds grunt-contrib-jshint. This suggests a shift towards a more comprehensive build and testing workflow. Dropping grunt-vows-runner and and adding grunt-contrib-jshint maybe represents change in the testing framework. grunt-contrib-jshint is a tool for JSHint code analysis.
For developers, this update could mean improved code correctness due to the addition of JSHint code analysis tool. While the core linting rules likely remain the same, the updated development dependencies provide a more modern testing and coverage setup, potentially streamlining contribution processes and ensuring higher code quality within the ESLint project itself. If you contribute to ESLint or rely on its internal workings, this change is noteworthy. If you're simply using ESLint for linting in your projects, the direct impact of this specific update might be minimal, but keeping up-to-date ensures you benefit from the latest improvements and bug fixes within the broader ESLint ecosystem.
All the vulnerabilities related to the version 0.1.3 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).
