@storybook/addon-actions versions 5.3.11 and 5.3.12 are both Action Logger addons for Storybook, designed to help developers track and visualize user interactions within their stories. The primary function remains consistent: logging actions triggered within components directly in the Storybook UI. This allows for easier debugging and understanding of how components respond to different events. Both versions share a common set of dependencies, including React, uuid, core-js, polished, prop-types, react-inspector and other @storybook dependencies like @storybook/api, @storybook/addons, @storybook/theming, @storybook/client-api, @storybook/components and @storybook/core-events ensuring a smooth integration with the Storybook ecosystem. They also share the same devDependencies for type definitions, ensuring a consistent development experience. This points to a stable core functionality and a focus on maintaining compatibility within the Storybook framework. The package size and file count remain the same implying that the changes are likely to be in the internal implementation.
The key difference lies in the updated versions of some of the core @storybook dependencies, specifically all those packages that have the version 5.3.11 in version 5.3.11 and 5.3.12 in version 5.3.12. Developers upgrading to version 5.3.12 will benefit from the improvements and bug fixes included in these updated Storybook packages. The version 5.3.12 was released a few hours after the version 5.3.11, being probably a patch. While the core functionality of logging actions remains the same, the upgrade is recommended to leverage the most recent enhancements within the Storybook platform, contributing to a more robust and efficient Storybook development workflow.
All the vulnerabilities related to the version 5.3.12 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:
