@storybook/addon-actions is a vital tool for Storybook users, enabling developers to easily display and log data received by actions in stories. Versions 5.3.2 and 5.3.1, while seemingly similar, offer key distinctions relevant to developers. The core functionality of logging actions remains consistent, focusing on providing immediate feedback on how components react to interactions within the Storybook environment. This allows for rapid validation of event handling and data flow during component development.
The primary difference between version 5.3.2 and 5.3.1 lies within their dependency versions. Upgrading from 5.3.1 to 5.3.2 pulls in the 5.3.2 versions of Storybook's internal packages such as @storybook/api, @storybook/addons, @storybook/theming, @storybook/client-api, @storybook/components and @storybook/core-events. This is important because these changes often incorporate bug fixes, performance improvements, and features across the entire Storybook ecosystem bundled in the related release. Althought not explicitly stated in the single addon release, this may result in subtle improvements in the action addon's performance, stability, or compatibility with other Storybook addons. The release dates indicate a quick follow-up, suggesting the update in 5.3.2 addresses potential issues or provides minor enhancements identified shortly after the release of 5.3.1. Developers should always aim to use the latest version to leverage the most up-to-date fixes and features within the @storybook/addon-actions package and the Storybook environment.
All the vulnerabilities related to the version 5.3.2 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:
