@storybook/addon-interactions is a valuable tool for Storybook users seeking to automate, test, and debug user interactions within their components. Version 6.4.21 builds upon the foundation laid by version 6.4.20, offering subtle enhancements and refinements. Primarily, the core dependencies are updated. For example, @storybook/api, @storybook/addons, @storybook/theming, @storybook/components, @storybook/core-common, and @storybook/core-events, and @storybook/instrumenter have all been bumped from version 6.4.20 to 6.4.21. This likely incorporates bug fixes, performance improvements, and potentially new features within those respective modules that directly benefit the interaction testing experience. Developers should see improvements that streamline the creation and execution of interaction tests, making it easier to verify the behavior of their components. Although fileCount and unpackedSize are identical, the crucial difference lies in the release date, with version 6.4.21 released after 6.4.20, indicating the newer version includes updates addressing issues present in the previous one and providing the most current stable features. Upgrading is generally recommended to take advantage of these potential improvements and maintain compatibility with the latest Storybook ecosystem. Ensure to compare the changelogs for the included dependencies @storybook/* to fully understand what is changed.
All the vulnerabilities related to the version 6.4.21 of the package
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.
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.
