Sass version 1.14.2 introduces a minor update to the popular Dart Sass implementation, building upon the stable foundation of version 1.14.1. Both versions provide a pure JavaScript solution for compiling Sass stylesheets, appealing to developers seeking a cross-platform and easily integrable Sass compiler. Key features remain consistent with the preceding version, including a dependency on the chokidar library for efficient file watching capabilities, essential for automatic recompilation during development workflows. Developers can rely on the MIT license, granting them flexibility in using and modifying the library. The core functionality of compiling Sass to CSS is consistent across both versions.
The primary difference between version 1.14.2 and 1.14.1 is a slight increase in the unpacked size, going from 708,398 bytes to 711,816 bytes. While the file count remains the same at 4, this subtle increase could indicate minor bug fixes, performance improvements, or small feature additions under the hood. From a developer's perspective, this change is unlikely to necessitate immediate action unless specific issues were encountered in 1.14.1 that are addressed in the newer release. The release date of 1.14.2 being October 11, 2018, compared to September 27, 2018, for 1.14.1 also suggests a relatively quick turnaround, further implying minor adjustments rather than groundbreaking alterations. Developers using Sass can likely upgrade to 1.14.2 with minimal disruption, benefiting from any incremental improvements implemented in the release. As with any update, testing is recommended to ensure compatibility within individual project environments.
All the vulnerabilities related to the version 1.14.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.
