@storybook/addon-actions versions 5.3.17 and 5.3.15 are both Action Logger addons for Storybook, facilitating the display of action dispatches within your stories. This allows developers to visually confirm the interactions and data flow within their components. While the core functionality remains consistent across these two versions, subtle differences exist primarily within their internal dependencies and release timing.
Specifically, examining the package data reveals updated dependencies for version 5.3.17, notably within the @storybook/* packages. The addon depends on @storybook/api, @storybook/addons, @storybook/theming, @storybook/client-api, @storybook/components, and @storybook/core-events, all bumped from 5.3.15 to 5.3.17. This increment suggests internal synchronisation across Storybook's ecosystem and possibly reflects bug fixes, performance improvements, or feature enhancements within those core packages.
Developers upgrading from 5.3.15 to 5.3.17 should benefit from a more cohesive Storybook experience. While the direct API of @storybook/addon-actions might not show significant changes, underlying stability and performance could be subtly improved due to the dependency updates. Furthermore, discrepancies in release dates confirm that 5.3.17 is a newer version, released after 5.3.15, implicitly incorporating any incremental changes and bug fixes accumulated during the interim. Therefore the newer version is preferrable for the last bug fixes and features.
All the vulnerabilities related to the version 5.3.17 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:
