Sass version 1.13.3 is a minor update to the widely used CSS preprocessor, building upon the foundation laid by version 1.13.2. Both versions, implemented purely in JavaScript, offer developers a robust solution for writing maintainable and scalable CSS. Focusing on what's new, the jump from 1.13.2 to 1.13.3 doesn't introduce significant breaking changes or new features, but contains small improvements. Comparing the two you can notice a slight change in the unpackedSize of the library from 691952 to 692621, suggesting minor fixes or optimization under the hood.
For developers already using Sass, this update presents a low-risk opportunity to benefit from the latest refinements. The core functionality, including features like variables, nesting, mixins, and functions, remains consistent between the two versions. The dependency on chokidar for file watching also remains unchanged, ensuring a smooth transition for those relying on automatic recompilation during development. The library is MIT licensed, and its source code is accessible in the dart-sass repository on GitHub, where you can examine the complete history and find more information.
All the vulnerabilities related to the version 1.13.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.
