The eslint library saw a minor version bump from 2.10.0 to 2.10.1, representing a quick improvement for this crucial JavaScript linting tool. Both versions share the same core dependencies, crucial for its functionality, including glob for file pattern matching, chalk for colorful console output, escope for ECMAScript scope analysis, and espree as the default JavaScript parser. Crucially, both versions rely on a robust set of utilities for parsing, traversing, and manipulating JavaScript code. The developer dependencies also remain consistent between versions.
The notable difference lies in the release date; version 2.10.1 came just a day after 2.10.0. This suggest a quick patch or bug fix was implemented in the newer version, although the specific details aren't evident from the provided data. Developers already using eslint 2.10.0 should consider upgrading to 2.10.1, especially if encountering any issues, as it potentially addresses unforeseen bugs or minor improvements. For those new to eslint, it provides a flexible and configurable way to enforce coding standards, identify potential errors, and improve overall code quality. Version 2.10.1 builds upon the solid foundation of 2.10.0, ensuring Javascript code adheres to defined styles and best practices, leading to more maintainable and robust applications.
All the vulnerabilities related to the version 2.10.1 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:
