ESLint version 2.13.0 represents a minor update to the popular JavaScript linting tool, building upon the foundation laid by version 2.12.0. Both versions share the core functionality of analyzing code for stylistic and programmatic errors, ensuring code quality and consistency across projects. Developers familiar with ESLint will find the upgrade seamless as the fundamental usage remains unchanged. The description and author are the same, and the MIT license continues to apply, indicating no shift in philosophy or maintainership.
The primary distinction lies in the updated dependencies. ESLint 2.13.0 upgrades the espree dependency from version 3.1.4 to 3.1.6. This is potentially important for developers utilizing newer JavaScript features or those relying on the most accurate parsing of ECMAScript syntax. espree is ESLint's core JavaScript parser; updates often include bug fixes and support for the latest language proposals. Reviewing the espree changelog for versions 3.1.5 and 3.1.6 is crucial to understand the specific impact this update has on your codebase. While other dependencies remain consistent between the two versions, this single update may address parsing issues encountered in 2.12.0 offering potentially better support and stability for current JavaScript standards. Staying current with ESLint ensures compatibility with the latest JavaScript specifications.
All the vulnerabilities related to the version 2.13.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:
