ESLint version 3.10.0 offers incremental improvements over version 3.9.1, primarily affecting dependency versions. While the core functionality of this widely-used JavaScript linting tool remains consistent, developers should note updates to its internal workings. In the "dependencies" section, the most notable change involves the ignore package, which progresses from version 3.1.5 to 3.2.0. This may introduce slight alterations in how ESLint handles ignored files and directories, potentially impacting projects with complex eslintignore configurations.
In "devDependencies", mock-fs sees an update rising from version 3.11.0 to 3.12.1. While a testing focused update, any updates on that package can improve how ESLint handles and deals with the local filesystem and mock filesystems when running tests. This might be of high interest to developers using mock-fs to manage unit tests. All other packages in both "dependencies" and "devDependencies" sections remain at the same version between the two releases.
Developers upgrading to 3.10.0 should review their ESLint configurations and testing setup, particularly focusing on file/directory exclusion patterns and any reliance on mocked file systems. While the updates appear minor, regressions or unexpected behavior can arise from internal dependency changes. Checking the changelog for both ignore and mock-fs packages for detailed lists of changes is always recommended to understand the update impact.
All the vulnerabilities related to the version 3.10.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:
