ESLint version 2.5.2 is a minor update to the popular JavaScript linting tool, building upon the foundation laid by version 2.5.1. Both versions share the core functionality of analyzing code for stylistic and potential errors based on a configurable set of rules. Crucially, the dependency trees for both versions are almost identical, meaning that core dependency functionality and versions remain largely the same. Developers can expect consistent behaviour in core linting functionality between the two versions, minimising the risk of unexpected bugs or integration issues during upgrades.
The key change distinguishing 2.5.2 stems in the eslint-release dev dependency, updated from version 0.4.0 to 0.4.1. While seemingly minor, this update likely addresses internal tooling improvements related to the ESLint release process itself like publishing, tagging and automating the release cycle. While not directly impacting linter functionality, such updates are valuable as they ensure the continued smooth delivery of future ESLint releases. Consequently, developers can upgrade from 2.5.1 to 2.5.2 with a high degree of confidence, enjoying the benefits of any underlying release process enhancements without the risk of introducing substantial changes to their linting configurations or workflows. Keep your ESLint updated, as it makes your code looks prettier.
All the vulnerabilities related to the version 2.5.2 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:
