Sass version 1.18.0 represents a minor point release in the evolution of this popular pure JavaScript implementation of the Sass stylesheet language. Comparing it to the immediately preceding stable version, 1.17.4, reveals several areas of interest for developers relying on Sass in their projects. Both versions share fundamental characteristics, including the same MIT license, dependency on chokidar version 2.0.0 or higher for file system watching capabilities, and originate from the same core Dart Sass project repository. The author remains Natalie Weizenbaum.
The updated version, 1.18.0, arrived quicker than the previous, being released on April 8, 2019, whereas 1.17.4 was released on April 3, 2019. While both distributions consist of 4 files within the package, a minor difference is observed in the unpacked size. Version 1.18.0 has 674891 bytes of unpacked content, slightly larger than the 674324 bytes of version 1.17.4. This suggests that 1.18.0 contains incremental tweaks, bug fixes, or minor feature augmentations leading to these differences. Ultimately, the changes should result to a superior experience for developers with an enhanced capability of handling stylesheets. While the core functionality and dependencies remain constant, the specific refinements of version 1.18.0 offer a subtly improved foundation for Sass compilation.
All the vulnerabilities related to the version 1.18.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.
