The @storybook/addon-actions package, a vital tool for Storybook users, allows developers to effortlessly display and inspect actions triggered within their components. Comparing versions 5.3.17 and 5.3.18 reveals subtle but important updates. Both versions share the same core dependencies, including essential libraries such as react, uuid, prop-types, and Storybook's internal packages like @storybook/api, @storybook/addons, and @storybook/components. They also incorporate development dependencies for TypeScript types, ensuring a smooth development experience. The key difference lies in the updated dependencies within the Storybook ecosystem itself. Version 5.3.18 upgrades its internal Storybook dependencies, such as @storybook/api, @storybook/addons, @storybook/theming, @storybook/client-api, @storybook/components, and @storybook/core-events from "5.3.17" to "5.3.18", aligning the addon with the broader Storybook environment. This synchronization likely includes bug fixes, performance improvements, and new features introduced within the core Storybook framework. Developers upgrading to 5.3.18 can expect enhanced stability, better compatibility with the latest Storybook features, and possibly access to improved debugging capabilities within the action logger. The upgrade ensures that the addon seamlessly integrates with the rest of the Storybook environment, maximizing its usefulness when recording user interactions in stories and component documentation.
All the vulnerabilities related to the version 5.3.18 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:
