Version 5.3.20 of @storybook/addon-actions primarily represents a maintenance release focused on internal updates and dependency alignment within the Storybook ecosystem. Comparing it to the prior stable version, 5.3.19, the core functionalities related to action logging in Storybook remain consistent. Developers leveraging @storybook/addon-actions to display action dispatches within their stories will find a familiar experience. The key changes reside in the synchronized versions of Storybook's internal packages.
Specifically, version 5.3.20 brings its dependencies @storybook/api, @storybook/addons, @storybook/theming, @storybook/client-api, @storybook/components, and @storybook/core-events to the 5.3.20 version, matching the parent package version. This synchronization ensures compatibility and stability across the Storybook environment, reducing potential conflicts arising from mismatched package versions. The underlying code related to action handling, argument display via react-inspector, and other user-facing features are practically untouched during this minor patch. The build process and file count also remain constant between versions. However, using the newest version assures developers are aligned with the most recent fixes and improvements within the Storybook framework itself. The release also includes an altered release date, showing it's a newer version.
All the vulnerabilities related to the version 5.3.20 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:
