Standard version 10.0.1 represents a minor update to the popular JavaScript Standard Style linter, building upon the foundation established by version 10.0.0. While both versions share core dependencies like eslint, standard-engine, and various ESLint plugins for Node.js, React, and import functionalities, key distinctions lie in the specific versions of some dependencies, particularly within the area of stylistic rules and JSX support.
The most notable change revolves around upgrades to peer dependencies related to ESLint configurations. Version 10.0.1 includes eslint-config-standard at version 10.2.0, a significant jump from 10.0.0 in the previous version, suggesting potential updates to the core JavaScript linting rules. Crucially, eslint-plugin-standard also sees an upgrade, moving from ~2.2.0 to ~3.0.1 indicating changes and fixes related to Standard's custom ESLint rules around best practices. Similarly, eslint-config-standard-jsx advances from version 3.3.0 to 4.0.1 which brings improvements and new functionalities to JSX linting, ensuring better compatibility and code quality within React projects.
For developers utilizing Standard, especially in React environments, these updates are particularly relevant. The enhanced JSX support and refined Standard rules contribute to more robust and consistent code style enforcement, reducing errors and improving overall code maintainability. Developers should review the changelogs for eslint-config-standard, eslint-plugin-standard, and eslint-config-standard-jsx to understand the specific rule changes and adjust their code accordingly to maintain compliance with the latest Standard Style guidelines and ensure best practices. The update promises more modern Javascript and React linting, while keeping the barrier to entry low.
All the vulnerabilities related to the version 10.0.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:
semver vulnerable to Regular Expression Denial of Service
Versions of the package semver before 7.5.2 on the 7.x branch, before 6.3.1 on the 6.x branch, and all other versions before 5.7.2 are vulnerable to Regular Expression Denial of Service (ReDoS) via the function new Range, when untrusted user data is provided as a range.
