@storybook/addon-actions versions 5.3.12 and 5.3.13, both action logger addons for Storybook, share a common foundation, providing developers with essential tools for capturing and displaying action events within their stories. Both versions list identical dependencies that include core libraries like React, uuid, global, core-js, polished, prop-types, fast-deep-equal, and react-inspector, ensuring compatibility and consistent behavior. Crucially, both rely on several internal Storybook packages like @storybook/api, @storybook/addons, @storybook/theming, @storybook/client-api, @storybook/components, and @storybook/core-events, tightly integrating into the Storybook ecosystem. Development dependencies for both remain the same, focusing on type definitions for uuid, lodash, and webpack environments.
The primary distinction lies in the version numbers of the internal @storybook/* dependencies. Version 5.3.13 upgrades these internal Storybook packages from 5.3.12 to 5.3.13. This indicates that version 5.3.13 likely incorporates bug fixes, performance improvements, or minor feature enhancements within Storybook's core components that trickle down to the addon-actions. For developers, this implies that upgrading from 5.3.12 to 5.3.13 ensures they're leveraging the latest refinements and stability improvements within the broader Storybook framework. Furthermore, the release date signifies a week difference suggesting a responsive maintenance cycle. This ensures developers have an up to date package from the maintainers.
All the vulnerabilities related to the version 5.3.13 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:
