@storybook/addon-actions versions 5.3.9 and 5.3.8 are action logger addons designed to enhance the Storybook development experience by recording and displaying actions performed within stories. Both versions share a common foundation, built around React and leveraging dependencies like uuid, global, core-js, polished, prop-types, fast-deep-equal, and react-inspector for core functionality. Crucially, both versions are tightly integrated with the Storybook ecosystem itself, depending on various @storybook/* packages such as @storybook/api, @storybook/addons, @storybook/theming, @storybook/client-api, @storybook/components, and @storybook/core-events. From a developer perspective, this allows seamless interaction and logging of events triggered within Storybook stories creating improved debugging capabilities.
While the core dependencies and functionalities remain largely the same between the two versions, the upgrade from 5.3.8 to 5.3.9 involved crucial updates within the Storybook ecosystem itself. The most notable difference lies in the versions of the @storybook/* dependencies these actions addon versions rely on. Version 5.3.9 adopts corresponding @storybook/* packages at version 5.3.9, where version 5.3.8 used the 5.3.8 versions of the same packages. This likely indicates bug fixes, performance improvements, or new features introduced across the broader Storybook platform that necessitated an update to the addon. Developers should upgrade to version 5.3.9 to ensure compatibility with the latest Storybook features and benefit from any underlying improvements and bug fixes within the core Storybook framework. The release date also shows that 5.3.9 was released a few days after 5.3.8 which strengthen the idea of a quick patch to solve some problems.
All the vulnerabilities related to the version 5.3.9 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:
