Sass version 1.17.1 represents a minor update to the popular Sass library, building upon the foundation laid by version 1.17.0. Both versions offer developers a pure JavaScript implementation of the Sass preprocessor, enabling them to leverage the power of Sass within their JavaScript-based projects. Key features remain consistent between the two, including the dependency on chokidar for file watching capabilities, facilitating automatic Sass compilation upon file changes. The MIT license ensures open-source flexibility for developers incorporating Sass into their projects.
The core functionality regarding Sass processing and its feature set are largely unchanged. However, a notable difference lies in the unpackedSize of the distribution, shrinking slightly from 683953 bytes in version 1.17.0 to 668445 bytes in version 1.17.1. This may indicate minor optimizations or reductions in bundled assets. Crucially, the release date reveals that version 1.17.1 was published on February 20, 2019, shortly after the release of version 1.17.0 on February 4, 2019. This relatively quick release suggests that version 1.17.1 likely addresses bug fixes, minor improvements, or potentially security patches identified swiftly after the initial 1.17.0 release. Developers are advised to upgrade to the latest 1.17.1 version to benefit from these potential improvements and ensure they are using the most stable and reliable iteration of the library within the 1.17.x series. The focus on bug fixes and optimization ensures efficient CSS pre-processing.
All the vulnerabilities related to the version 1.17.1 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.
