Standard.js version 6.0.8 represents a subtle but important update to the popular JavaScript Standard Style linter, released on March 7, 2016. The core difference between this version and the previous stable release, 6.0.7, primarily lies in its dependency on ESLint. Version 6.0.8 updates ESLint to version ~2.2.0, whereas version 6.0.7 depends on version ^2.1.0. This seemingly small change can have ripple effects for developers, introducing potential linting rule changes dictated by the updated ESLint core.
While other dependencies like xtend, standard-engine, and various eslint-plugin-* packages remain consistent, the updated ESLint version ensures developers are benefiting from the latest bug fixes, performance improvements, and potentially new ECMAScript features supported by the linter. Developers upgrading should be aware of ESLint's changelog from 2.1.0 to 2.2.0 to anticipate any rule changes that could affect their codebase. The update doesn't introduce new features directly within Standard.js itself, but it ensures the linter's capabilities are aligned with the evolving JavaScript landscape through its core linter dependency, ESLint. For existing users and especially in projects already using the 6.x branch, upgrading to 6.0.8 is generally recommended to maintain compatibility and benefit from the improvements in ESLint. New users will automatically receive these updates.
All the vulnerabilities related to the version 6.0.8 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:
