Rollup Plugin Sass saw a minor version bump from 1.1.0 to 1.2.0 on March 28, 2019, offering developers a few key improvements for integrating Sass stylesheets into their Rollup-based projects. Both versions provide the core functionality of compiling .sass files during the Rollup bundling process, simplifying workflow and ensuring consistent styling across applications. Key dependencies like pify, sass, resolve, fs-extra, babel-runtime, and rollup-pluginutils remain consistent between the versions, indicating that the core compilation process and compatibility with Babel remain unchanged.
The most notable difference lies in the addition of development dependencies for testing and code quality in version 1.2.0. Specifically, nyc for code coverage, coveralls for reporting coverage, have been added. This signals an increased focus on maintainability and reliability of the plugin. While the core functionality remains largely the same, developers can benefit from the increased confidence in the plugin's stability that comes with enhanced testing infrastructure. The slight increase in file count and unpacked size in 1.2.0 likely reflects included testing files and configuration. Users upgrading from 1.1.0 should experience seamless integration with enhanced reliability.
All the vulnerabilities related to the version 1.2.0 of the package
Uncontrolled resource consumption in braces
The NPM package braces fails to limit the number of characters it can handle, which could lead to Memory Exhaustion. In lib/parse.js, if a malicious user sends "imbalanced braces" as input, the parsing will enter a loop, which will cause the program to start allocating heap memory without freeing it at any moment of the loop. Eventually, the JavaScript heap limit is reached, and the program will crash.
Regular Expression Denial of Service (ReDoS) in micromatch
The NPM package micromatch prior to version 4.0.8 is vulnerable to Regular Expression Denial of Service (ReDoS). The vulnerability occurs in micromatch.braces() in index.js because the pattern .* will greedily match anything. By passing a malicious payload, the pattern matching will keep backtracking to the input while it doesn't find the closing bracket. As the input size increases, the consumption time will also increase until it causes the application to hang or slow down. There was a merged fix but further testing shows the issue persisted prior to https://github.com/micromatch/micromatch/pull/266. This issue should be mitigated by using a safe pattern that won't start backtracking the regular expression due to greedy matching.
