@storybook/addon-actions versions 5.3.21 and 5.3.20 offer developers a powerful tool for logging actions within their Storybook environment, enhancing the development and debugging experience of React components. Both versions share a common foundation, providing the core functionality of capturing and displaying dispatched actions triggered by user interactions within stories. Key dependencies like uuid, react, core-js, polished, and prop-types remain consistent, ensuring compatibility and leveraging well-established libraries for their respective functions.
The upgrade from 5.3.20 to 5.3.21 involves subtle internal improvements and likely bug fixes, as reflected in the minor version increment. While the core API and functionality remain largely the same, developers should consider upgrading to version 5.3.21 to benefit from the latest enhancements and potential stability improvements. Both versions include essential Storybook dependencies such as @storybook/api, @storybook/addons, @storybook/theming, @storybook/client-api, @storybook/components, and @storybook/core-events, ensuring seamless integration within the Storybook ecosystem. The development dependencies, including @types/uuid, @types/lodash, and @types/webpack-env, also remain the same, indicating no major changes in the development environment or build process. The most noticeable differenceis the release date, with version 5.3.21 released two days after 5.3.20. Developers leveraging @storybook/addon-actions can expect a reliable action logging solution, simplifying the process of verifying component behavior and interaction within their Storybook stories.
All the vulnerabilities related to the version 5.3.21 of the package
Cross site scripting in markdown-to-jsx
Versions of the package markdown-to-jsx before 7.4.0 are vulnerable to Cross-site Scripting (XSS) via the src property due to improper input sanitization. An attacker can execute arbitrary code by injecting a malicious iframe element in the markdown.
ReDOS vulnerabities: multiple grammars
The Regular expression Denial of Service (ReDoS) is a Denial of Service attack, that exploits the fact that most Regular Expression implementations may reach extreme situations that cause them to work very slowly (exponentially related to input size). An attacker can then cause a program using a Regular Expression to enter these extreme situations and then hang for a very long time.
If are you are using Highlight.js to highlight user-provided data you are possibly vulnerable. On the client-side (in a browser or Electron environment) risks could include lengthy freezes or crashes... On the server-side infinite freezes could occur... effectively preventing users from accessing your app or service (ie, Denial of Service).
This is an issue with grammars shipped with the parser (and potentially 3rd party grammars also), not the parser itself. If you are using Highlight.js with any of the following grammars you are vulnerable. If you are using highlightAuto to detect the language (and have any of these grammars registered) you are vulnerable. Exponential grammars (C, Perl, JavaScript) are auto-registered when using the common grammar subset/library require('highlight.js/lib/common') as of 10.4.0 - see https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@10.4.0/build/highlight.js
All versions prior to 10.4.1 are vulnerable, including version 9.18.5.
Grammars with exponential backtracking issues:
And of course any aliases of those languages have the same issue. ie: hpp is no safer than cpp.
Grammars with polynomial backtracking issues:
And again: any aliases of those languages have the same issue. ie: ruby and rb share the same ruby issues.
If you have any questions or comments about this advisory:
