ESLint version 3.0.1 represents a minor update to the popular JavaScript linting tool, building upon the 3.0.0 release. Both versions aim to provide developers with a robust and configurable way to enforce coding standards and identify potential errors in their JavaScript code. Core functionalities such as AST-based pattern checking, extensive rule sets, and customizable configurations remain consistent.
The primary distinction between versions lies in dependency updates and bug fixes. Examining the dependencies list, version 3.0.1 removes its dependency for path-is-absolute, this might indicate a refinement in how ESLint handles path resolution or a reliance on a different internal module. While both versions share almost the same devDependencies, suggesting a continuity in the testing and build processes, the minor version increment implies that 3.0.1 likely addresses specific issues reported in 3.0.0, possibly improving stability or resolving compatibility concerns. Developers using ESLint should strongly consider the update to 3.0.1 mainly for bug fixes, potentially improving the overall linting experience and integrating smoothly within existing workflows. Consider exploring the [official ESLint blog](https://eslint.org/blog/) or GitHub repository to know more about the bug fixes or potential changes in behavior, and use a tool like npm diff to have a complete overview of the changes.
All the vulnerabilities related to the version 3.0.1 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:
