Sass version 1.15.2 presents a minor update over its predecessor, 1.15.1, within the popular Dart Sass library. Both versions maintain the core functionality of providing a pure JavaScript implementation of Sass, a powerful CSS preprocessor that enhances styling workflows with features like variables, nesting, and mixins. Developers using either version can expect consistent Sass compilation capabilities directly within JavaScript environments, without external dependencies on Ruby.
The key difference lies in the details of the release. While the dependencies on 'chokidar' remain the same, indicating no changes in file watching capabilities, the 'unpackedSize' metric within the 'dist' object reveals a slight decrease from 696515 to 696427. This suggests minor optimizations or refinements in file size contributing to a slightly more efficient package. The release date also marks a difference as version 1.15.2 was published on December 6th, 2018, approximately three weeks after version 1.15.1 which was released on November 16th, 2018. For developers, this incremental update likely means small improvements and bug fixes, reinforcing the stability and reliability of the Sass compiler within their projects. Keeping up with such minor releases is still important for those of us who aim for greater optimization, stability and the best possible DX.
All the vulnerabilities related to the version 1.15.2 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.
