ESLint 3.15.0 represents an iteration of the popular JavaScript linting tool, building upon the capabilities offered in version 3.14.1. Both versions share the core function of analyzing JavaScript code for potential errors, style inconsistencies, and adherence to best practices, leveraging an AST-based approach. Developers familiar with ESLint will find the fundamental usage and configuration principles remain largely consistent.
A notable distinction lies in the updated dependencies. While many dependencies remain consistent, ESLint 3.15.0 utilizes espree "^3.4.0" reflecting an enhancement of the JavaScript parser. Conversely, version 3.14.1 depends on espree "^3.3.1". Differences in minor versions like this often signify bug fixes, performance improvements, or support for newer JavaScript syntax features made available in the newer version. Developers leveraging newer JavaScript features could benefit from the updated espree parser in the newer version due to its enhanced support .
It's worth examining the ESLint changelog for more granular details about specific rule updates, bug fixes, and performance tweaks introduced in 3.15.0 but from these json we can only see that the espree dependency was updated. Consider upgrading to the latest stable version (check other releases after this one for newer features), as the update of the espree parser can include fixes and advantages when working with new Javascript code.
All the vulnerabilities related to the version 3.15.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:
