Gulp-sass-lint offers a streamlined approach to integrating Sass linting into your Gulp workflows, ensuring code quality and consistency across your stylesheets. Comparing version 1.4.0 with the previous stable release, 1.3.4, reveals key improvements for developers. The most notable change lies in the dependency updates. Version 1.4.0 replaces gulp-util, a somewhat broad utility library, with the more focused plugin-error. This change suggests a move towards more specific error handling within the plugin, potentially leading to more informative and relevant error messages during the linting process. Developers should benefit from clearer feedback when Sass linting rules are violated. Both versions maintain the core dependencies of sass-lint and through2, ensuring compatibility with existing Sass linting configurations and efficient stream processing for Gulp. The sass-lint dependency remains at "^1.12.0" in both versions, indicating no changes in linting rules or core functionality between the releases concerning the linter itself. Furthermore, the developer dependencies, including gulp, remain consistent, ensuring that upgrading gulp-sass-lint doesn't necessitate significant changes to existing Gulp build processes. Version 1.4.0 was released in May 2018, roughly seven months after version 1.3.4 indicating continued maintenance. Ultimately, upgrading to version 1.4.0 provides a more targeted and maintainable plugin with better error handling and no breaking changes, solidifying gulp-sass-lint as a robust choice for automating Sass linting and enforcing code quality standards.
All the vulnerabilities related to the version 1.4.0 of the package
Prototype Pollution in merge
All versions of package merge <2.1.1 are vulnerable to Prototype Pollution via _recursiveMerge .
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:
