@storybook/addon-actions provides developers with a powerful tool for logging actions triggered within Storybook stories, enhancing the debugging and testing workflow. Examining versions 5.3.0 and 5.3.1, we can see a subtle but crucial difference. Version 5.3.1, released merely a day after 5.3.0, incorporates updated dependencies for other core Storybook packages like @storybook/api, @storybook/addons, @storybook/theming, @storybook/client-api, @storybook/components, and @storybook/core-events. These are all bumped from 5.3.0 to 5.3.1. While the core functionality of action logging remains consistent, this update ensures compatibility and improved integration with the broader Storybook ecosystem.
Developers leveraging @storybook/addon-actions benefit from clear, concise logs of dispatched actions, empowering them to readily inspect event payloads and confirm proper application behavior. The addon seamlessly integrates with React components, utilizing familiar dependencies like uuid, react, prop-types, and react-inspector for enhanced data visualization. The inclusion of core-js ensures broader browser compatibility, and polished aids in styling consistency.
For users seeking the most stable and up-to-date experience, upgrading to @storybook/addon-actions version 5.3.1 is advisable. This ensures that your action logs are aligned with the latest improvements and bug fixes in the core Storybook framework, minimizing potential conflicts and providing a smoother development process. Remember to update all @storybook/* packages together for optimal performance and dependency resolution.
All the vulnerabilities related to the version 5.3.1 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:
