ESLint version 3.11.1 is a minor patch release following 3.11.0 in the popular JavaScript linting tool. Both carry the same core description: "An AST-based pattern checker for JavaScript," highlighting ESLint's foundation in abstract syntax trees, enabling robust and precise code analysis. Examining the data, the primary difference lies in the release date, with version 3.11.1 published on November 28, 2016, shortly after version 3.11.0 on November 25, 2016.
For developers, the significance of a patch release like 3.11.1 lies in its potential to address bugs, security vulnerabilities, or performance issues present in the preceding version. While the provided data snippets indicate no specific changes in dependencies or development dependencies between the two versions, users should consult the official ESLint changelog for a detailed breakdown of the fixes included in 3.11.1.
This incremental update underscores the importance of staying current with ESLint versions. Patch releases often contain crucial improvements that enhance code quality, stability, and security. Developers relying on ESLint for their JavaScript projects should prioritize upgrading to the latest patch version to benefit from these enhancements and maintain a robust development environment. The detailed dependency lists are identical, showcasing the stability of the core components used by the linter.
All the vulnerabilities related to the version 3.11.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:
