Sass version 1.20.3 represents a minor update to the popular CSS preprocessor, building upon the foundation laid by its predecessor, version 1.20.1. Both versions utilize Chokidar for file watching capabilities, ensuring efficient compilation on changes. The core functionality remains consistent, delivering a pure JavaScript implementation of Sass that developers can seamlessly integrate into their projects. The MIT license continues to provide developers with the freedom to use, modify, and distribute the library.
While the fundamental features are shared, a key difference lies in the increased unpacked size of version 1.20.3, which at 693034 bytes is slightly larger than version 1.20.1's 676648 bytes, suggesting the incorporation of new features, optimizations, or expanded assets. Developers should note this difference if disk space is a constraint. Moreover, version 1.20.3 was released on May 31, 2019, marking a later release date than version 1.20.1, released on May 3, 2019. This suggests that the newer version incorporates bug fixes, performance improvements, or minor feature enhancements accumulated during the intervening period. Developers should always prioritize the most recent stable release to benefit from the latest improvements and fixes. Ultimately, both versions offer the robust Sass functionalities, but developers should analyze the small differences to decide appropriately about which one is better for their projects.
All the vulnerabilities related to the version 1.20.3 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.
