Sass version 1.22.0 introduces incremental improvements over the preceding stable release, version 1.21.0, focusing on refinements rather than groundbreaking new features. Both versions maintain the core functionality of a pure JavaScript implementation of Sass, enabling developers to seamlessly integrate Sass compilation into JavaScript-based projects. Key characteristics remain constant, such as the dependency on chokidar for file watching capabilities, crucial for automated Sass recompilation during development. The MIT license prevails, ensuring permissibility for use in various project types. Natalie Weizenbaum continues to be credited as the author.
However, a noteworthy difference lies in the "unpackedSize" attribute within the "dist" object. Version 1.22.0 indicates a size of 730870 bytes, subtly larger than version 1.21.0 which has 703534. This increase, although minor, suggests potential enhancements, bug fixes, or expanded functionalities incorporated within the newer release. The release dates, June 25, 2019, for 1.22.0 and June 6, 2019, for 1.21.0, establish a short interval between releases, indicative of an active maintenance cycle. Developers might find the update worthwhile to benefit from the latest bug fixes, performance improvements, and refinements. While the core functionality remains consistent, the updated version could potentially offer a slightly optimized or more robust experience. Both versions guarantee a reliable Sass compilation within JavaScript environments, a core selling point for frontend developers.
All the vulnerabilities related to the version 1.22.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.
