ESLint version 2.1.0 is a minor update to the AST-based JavaScript pattern checker, building upon the solid foundation of version 2.0.0. Both versions share the core functionality of analyzing JavaScript code for stylistic and potential error patterns, ensuring code quality and consistency. The key difference lies in the dependency updates and potential bug fixes incorporated in the newer release.
Developers upgrading from 2.0.0 will find largely familiar territory, as core functionalities remain consistent. The dependency list for ESLint 2.1.0 sees a notable change in inquirer, moving from version 0.11.0 to 0.12.0. Those using inquirer directly through ESLint’s configuration or tooling may need to check for compatibility. Version 2.1.0 includes eslint-release which is missing in version 2.0.0 and removes mocha-phantomjs package in devDependencies of version 2.0.0 that it is considered an important change that leads to upgrading to the new major version.
For developers already leveraging the robust features of ESLint 2.0.0, the 2.1.0 release presents a low-risk upgrade path to benefit from the latest dependency updates, optimizations, and bug fixes potentially enhancing stability and performance. New adopters will find a mature and powerful linting tool in either version, empowering them to enforce coding standards and improve code maintainability within their JavaScript projects. Always remember to test after upgrading to ensure there are no unexpected side effects.
All the vulnerabilities related to the version 2.1.0 of the package
Prototype Pollution in Ajv
An issue was discovered in ajv.validate() in Ajv (aka Another JSON Schema Validator) 6.12.2. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code.)
Improper Privilege Management in shelljs
shelljs is vulnerable to Improper Privilege Management
Improper Privilege Management in shelljs
Output from the synchronous version of shell.exec() may be visible to other users on the same system. You may be affected if you execute shell.exec() in multi-user Mac, Linux, or WSL environments, or if you execute shell.exec() as the root user.
Other shelljs functions (including the asynchronous version of shell.exec()) are not impacted.
Patched in shelljs 0.8.5
Recommended action is to upgrade to 0.8.5.
https://huntr.dev/bounties/50996581-c08e-4eed-a90e-c0bac082679c/
If you have any questions or comments about this advisory:
