ESLint version 3.12.0 represents a minor update to the popular JavaScript linting tool, building upon the foundation laid by version 3.11.1. While the core functionality remains consistent, developers should note subtle changes in dependency versions, particularly concerning the globals package, which progresses from version 9.2.0 to 9.14.0. This impacts the pre-defined global variables recognized by ESLint, potentially affecting code analysis and rule adherence. This could introduce new global variables to your linting environment. The release date also gives an idea of when it was released.
Developers relying on specific global variable definitions should review their configurations to ensure compatibility with the updated globals package. Otherwise, the core dependencies remain largely unchanged, preserving the familiar linting environment. The development dependencies are identical, suggesting no significant alterations to the testing or build processes between versions. The release data indicates a relatively short interval between the two versions, implying a focused effort on incremental improvements and bug fixes. While the differences might seem subtle, staying up-to-date with dependency versions is crucial for maintaining a stable and predictable linting workflow, ultimately ensuring code quality and consistency across projects. The consistency in development dependencies indicates a stable development process.
All the vulnerabilities related to the version 3.12.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:
