eslint 2.11.0 refines the functionality of the popular JavaScript linting tool, building upon the foundation laid by version 2.10.2. Both versions share core dependencies like glob, chalk, lodash, and espree, ensuring consistent file handling, output formatting, utility functions, and JavaScript parsing. Developers familiar with 2.10.2 will find a seamless transition to the new version and similar behavior overall.
A main difference resides in the timing, a gap of roughly 10 days between releases indicates problem solving and bug-fixing. Version 2.11.0 benefits from the fixes and tweaks which were applied within that period, so users will find a better and more stable experience. No major changes are mentioned, but this points to improvements of the existing rules and edge cases.
Developers using eslint benefit from AST-based analysis which guarantees an accurate analysis of their code, with support for the latest ECMAScript features. The extensibility through custom rules and plugins enables adaptation to specific project needs and coding styles. Comprehensive configuration options and integration with popular editors and build tools streamline adoption. Both versions emphasize code quality, consistency, and maintainability, aiding developers in writing cleaner and more robust JavaScript. Choosing 2.11.0 gives acces to fine tuned stability and greater efficiency, even when based on a similar Dependency Injection.
All the vulnerabilities related to the version 2.11.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:
