ESLint version 2.10.2 arrives shortly after 2.10.1, offering subtle but potentially crucial updates for JavaScript developers relying on this popular linting tool. While the core functionality remains consistent, a closer inspection reveals key modifications within the development dependencies. Most notably, karma-mocha-reporter and karma-phantomjs-launcher are introduced in 2.10.2, suggesting improvements or changes in the testing setup and reporting mechanisms. These additions would primarily impact developers involved in the testing and continuous integration processes, potentially streamlining test result analysis and improving the overall testing workflow. Conversely, version 2.10.1 included mocha-phantomjs and phantomjs-polyfill as dev dependencies that were removed from 2.10.2. This may indicate a shift in supported testing environments or a reorganization of testing dependencies, which could impact developers who have built custom testing workflows relying on these specific packages. Examining the changelog or related release notes is highly recommended to understand the precise rationale behind these changes and their potential impact on existing projects. The core dependencies, which directly influence the linting rules and functionalities, remain unchanged, implying that the fundamental linting behavior and rule configurations should remain stable between these two versions. The date change shows that the updated version was released 2 days after.
All the vulnerabilities related to the version 2.10.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:
