ESLint version 2.5.3 is a minor update to the popular JavaScript linting tool, building upon the solid foundation of version 2.5.2. Both versions share the same core functionality, providing developers with robust static analysis capabilities to identify and fix coding style issues, potential errors, and enforce best practices within their JavaScript projects. Core dependencies remain consistent between the two versions, ensuring feature of glob, chalk, debug, table, escope, espree, ignore, lodash and other key packages operate in a predictable manner.
A key difference lies in the updated "eslint-release" dev dependency. Version 2.5.3 depends on "eslint-release":"^0.5.0" while it was "eslint-release":"^0.4.1" in the previous version. Such changes often incorporate bug fixes, enhancements to the release process itself, or compatibility adjustments for the tooling used to create and distribute ESLint. The "releaseDate" metadata also shows that version 2.5.3 was released shortly after 2.5.2, it is likely addressing a bug fix.
Developers should consider upgrading to version 2.5.3 to benefit from the latest improvements and bug fixes within the ESLint release infrastructure. While the core linting rules and functionalities are generally consistent, staying up-to-date with minor releases ensures a smoother development workflow and avoids potential issues related to the release tooling. Examine the changelog for the eslint-release package to pinpoint the specific changes incorporated in release 0.5.0. This upgrade helps to maintain code quality and consistency across projects, making it an essential tool for professional JavaScript development.
All the vulnerabilities related to the version 2.5.3 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:
