Standard.js version 8.1.0 represents a subtle but important update to the popular JavaScript Standard Style linter. Released on September 17, 2016, it refines the developer experience over its predecessor, version 8.0.0, which came out on August 24, 2016. A key difference lies in the updated dependency management. Version 8.1.0 upgrades eslint from ~3.3.1 to ~3.5.0, and eslint-config-standard is updated from 6.0.0-beta.3 to 6.0.1. These updates translate to the latest linter rules and configurations, ensuring code adheres to the established Standard Style guidelines.
For developers, this means potentially fewer linting errors and a more consistent codebase, immediately. The adjustments to eslint-config-standard specifically signal improvements and refinements in how Standard Style's core rules are applied. While the other dependencies, including standard-engine, eslint-plugin-react, eslint-plugin-promise, eslint-plugin-standard, eslint-config-standard-jsx, and the devDependencies, remain consistent between the two versions, these key ESLint upgrades make version 8.1.0 the recommended choice for new projects and an advisable update for existing ones. Staying current with these point releases helps maintain compatibility and benefits from ongoing improvements in the underlying linting engine and rule sets, contributing to better code quality and maintainability.
All the vulnerabilities related to the version 8.1.0 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:
