ESLint version 3.11.0 represents an incremental update to the popular JavaScript linting tool, building upon the foundation laid by version 3.10.2. While both versions share the core functionality of AST-based pattern checking and code style enforcement, subtle shifts in dependencies and development tools can impact the developer experience.
A key difference lies in the updated markdownlint devDependency, moving from version 0.2.0 to 0.3.1. This suggests improvements and bug fixes to the Markdown linting rules used in ESLint's documentation and internal processes, ensuring higher quality documentation and potentially better performance related to markdown processing. The core dependencies remain the same, indicating stability in the fundamental linting engine. Developers can expect consistent behavior in terms of core JavaScript analysis and rule enforcement. The releaseDate also highlights a recent update, implying access to the latest bug fixes and refinements.
For developers using ESLint, these changes signal a stable upgrade path. With consistent core dependencies the update is unlikely to introduce breaking changes. The updated markdownlint dependency ensures higher quality documentation making this an attractive update for teams focused on coding standards, code quality, and maintainability. Always consult the official changelog for a comprehensive list of changes and specific migration guidance.
All the vulnerabilities related to the version 3.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:
