Standard version 7.1.1 represents a minor patch release over version 7.1.0, both iterations of the popular JavaScript Standard Style linter. The core functionality remains consistent, providing a straightforward and opinionated approach to JavaScript code formatting and style enforcement. Developers adopting Standard benefit from its zero-configuration setup, ensuring consistent code style across their projects without wrestling with complex configuration files.
Comparing the two versions, the key difference lies in the "cross-spawn" dependency within the *devDependencies*, which changed from "cross-spawn-async":"^2.1.8" in 7.1.0 to "cross-spawn":"^3.0.1" in 7.1.1. This indicates a likely update or change in the underlying tooling used for cross-platform process spawning during development or testing. While not directly impacting the end-user experience of linting, this change suggests improvements in the development workflow or bug fixes related to process management. Both versions share the same core dependencies like ESLint, standard-engine, and various ESLint plugins for React, Promise, and Standard rules, guaranteeing a consistent linting experience. The release date difference further emphasizes the incremental nature of the 7.1.1 update, suggesting it addresses minor issues found after the initial 7.1.0 release. For developers, upgrading to 7.1.1 ensures they are using the latest and potentially most stable version of the development tooling, benefiting from any under-the-hood improvements and bug fixes.
All the vulnerabilities related to the version 7.1.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:
