Sass version 1.13.2 presents a subtle but noteworthy update over its predecessor, 1.13.1. Both versions share the same core functionality as a pure JavaScript implementation of the popular Sass CSS preprocessor, offering developers a way to write more organized and maintainable stylesheets. They both rely on chokidar for file watching capabilities, indicating a continued investment in efficient development workflows. The licensing and repository details remain consistent, as does the authorship.
The interesting improvements for developers are not explicitly stated, we understand that version 1.13.2 likely includes bug fixes and minor performance enhancements that improve the developer experience. The file count remains steady at four, suggesting only internal code changes occurred. Moreover, the unpacked size shows a slight increase from 691,610 bytes in 1.13.1 to 691,952 bytes in the newer release. This increment points to additional code or refinements contributing to the package's overall functionality or stability. Released on September 5th, 2018, version 1.13.2 arrived just a few days after 1.13.1, signifying a quick iteration cycle presumably aimed at addressing immediate issues or improvements identified in the prior version.
All the vulnerabilities related to the version 1.13.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.
