Sass version 1.19.0 represents a minor update over its predecessor, version 1.18.0, continuing its mission to provide a pure JavaScript implementation of Sass. Both versions rely on the chokidar library for file watching capabilities. While the core functionality remains largely consistent, subtle refinements are evident in the updated release.
Developers considering upgrading from 1.18.0 to 1.19.0 should note the small increment in unpackedSize, suggesting potential under-the-hood optimizations or minor feature additions. These internal adjustments are unlikely to introduce breaking changes but could contribute to improved performance. The primary difference between the versions lies in the release date: version 1.19.0 was released on April 19, 2019, approximately 10 days after the previous version. This indicates a relatively rapid iteration cycle, possibly in response to bug fixes or small enhancements identified in version 1.18.0.
Though not explicitly detailed in the provided data, improvements in compilation speed, bug fixes related to specific Sass language features, or enhanced compatibility with certain Node.js versions are likely candidates for the changes implemented. Users encountering specific issues with 1.18.0 might find 1.19.0 a worthwhile upgrade. As with any library update, running tests of your project using the newest version of Sass is highly recommended before deploying the new version in a production enviroment.
All the vulnerabilities related to the version 1.19.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.
