@storybook/addon-actions is a valuable tool for Storybook users, enabling developers to easily display and inspect actions triggered within their components during development and testing. Comparing versions 5.3.18 and 5.3.19 reveals subtle yet important differences primarily in the interconnected Storybook ecosystem. The core functionality of logging actions remains consistent, allowing developers to capture event data associated with user interactions within stories.
The key distinction lies in the synchronized versioning of dependent @storybook packages. Version 5.3.19 upgrades dependencies on internal Storybook packages like @storybook/api, @storybook/addons, @storybook/theming, @storybook/client-api, @storybook/components, and @storybook/core-events to version 5.3.19, ensuring better compatibility and potentially incorporating bug fixes or enhancements from those related modules. Version 5.3.18 uses 5.3.18 versions of those packages. While the core dependencies of react, uuid, and others remain the same, this coordinated update within the Storybook ecosystem guarantees a smoother experience, reducing the risk of version mismatches and unexpected behavior. For developers, upgrading to 5.3.19 translates to improved stability and access to the latest features across the entire Storybook platform, making it a worthwhile update for projects already leveraging Storybook. Ultimately, using the latest version as part of a well-maintained Storybook project delivers the best and most consistent developer experience. The release date difference also shows that this is a somewhat recent and maintained library.
All the vulnerabilities related to the version 5.3.19 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:
