@storybook/addon-interactions, a valuable tool for automating, testing, and debugging user interactions within Storybook, released versions 6.4.21 and 6.4.22 in close succession. Both versions maintain the same core functionality, offering developers features to easily create interaction tests directly within their Storybook stories. This enables a streamlined workflow for visually confirming component behavior and identifying potential issues early in the development process. The addon leverages tools like Jest and Testing Library under the hood, enabling familiar testing patterns. A key benefit is the reduced context switching required, as developers can seamlessly transition from building components to testing their interactivity within the same environment.
The primary visible difference between versions 6.4.21 and 6.4.22 lies in the updated dependencies of other Storybook packages. Specifically, dependencies such as @storybook/api, @storybook/addons, @storybook/theming, @storybook/components, @storybook/core-common, and @storybook/core-events have been bumped from version 6.4.21 to 6.4.22. While the core functionality of the addon itself remains unchanged, this dependency update likely incorporates bug fixes, performance improvements, or new features within those core Storybook modules. Therefore, upgrading to 6.4.22 is recommended to ensure compatibility and benefit from the latest enhancements across the Storybook ecosystem. Both versions rely on peer dependencies of React and React DOM, ensuring compatibility with common frontend setups.
All the vulnerabilities related to the version 6.4.22 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.
