ESLint version 2.6.0 introduces subtle but potentially impactful changes compared to its predecessor, version 2.5.3. The core functionality, an AST-based pattern checker for JavaScript, remains consistent, ensuring a smooth transition for existing users. However, developers should note some dependency updates. Most notably, the chalk dependency has been updated from version 1.0.0 to ^1.1.3. This update primarily affects the styling of ESLint's output in the console, potentially improving readability and aesthetics through enhanced color support and features. A less noticeable but also important change is the removal of the resolve package in the newer version. This suggests changes in how ESLint handles module resolution, which savvy developers may want to investigate further to ensure compatibility with custom configurations or plugins.
Both versions leverage the same core engines like escope, espree, and estraverse for static analysis, with the critical versions remaining unchanged. They also share a wide range of devDependencies to cover testing, building, and other development lifecycle tasks. Users who find value in formatted console outputs can appreciate the chalk update. Developers should assess how module resolution changes impact their specific projects. Overall, for most users the transition should be safe, given the focus on dependency changes and a consistent eslint engine.
All the vulnerabilities related to the version 2.6.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:
