Standard version 6.0.2 represents a subtle but potentially important upgrade over version 6.0.1 for developers leveraging the popular JavaScript Standard Style. Both versions share a common foundation, built around eslint for linting and standard-engine for core functionality. They also maintain identical development dependencies for testing and tooling.
The critical distinctions reside within the dependencies section. Version 6.0.2 upgrades eslint-config-standard from version 5.0.0 to 5.1.0 and eslint-config-standard-jsx from version 1.0.0 to 1.1.0. These eslint-config-standard packages define the specific linting rules enforced by Standard, suggesting that version 6.0.2 incorporates updates to the standard rules themselves, or the way they are applied. While seemingly minor version bumps, these changes could introduce new or modified linting behaviors. Developers should examine the changelogs for eslint-config-standard v5.1.0 and eslint-config-standard-jsx v1.1.0 to understand the specific rule adjustments.
If developers are seeking utmost consistency, sticking with version 6.0.1 might be preferred. However, adopting 6.0.2 enables them to use the latest officially curated Standard Style rules. Keep in mind that standard enforce consistent code style to increase code quality and readability within your projects. Also, by using the latest version of standard they can also benefit from the new features and vulnerability fixes that are introduced. Choosing the right version will depend on your project requirements.
All the vulnerabilities related to the version 6.0.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:
