Eslint version 3.3.1 is a minor update to the popular JavaScript linting tool, building upon the features and stability of version 3.3.0. Both versions share the same core functionality: providing AST-based pattern checking to help developers enforce consistent coding styles and identify potential errors in their JavaScript code. They include a rich set of dependencies like glob for file matching, escope for scope analysis, and espree as the default parser, ensuring robust and accurate code analysis.
The difference between the versions lies primarily in bug fixes and minor enhancements, aimed at improving the overall developer experience. While the core dependency versions remain largely the same, the update likely addresses specific issues reported by the community and found internally to enhance stability and performance. This continues to include powerful features such as custom rule creation, configurable linting rules, and integrations with various IDEs and build tools.
Developers upgrading from 3.3.0 to 3.3.1 can expect a smoother and more reliable linting process. Although the changes may not be immediately apparent, especially if the previous version was already working well, the underlying improvements contribute to a more robust toolchain. The updated version maintains the same MIT License and repository location, making it a straightforward update for existing users. The precise fixes would be listed in the changelog for that update.
All the vulnerabilities related to the version 3.3.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:
