@storybook/addon-actions is a vital tool for Storybook users, streamlining the process of logging actions triggered within your components for easy debugging and interactive documentation. Comparing versions 5.3.4 and 5.3.3 reveals subtle but important refinements. While the core functionality remains consistent, several internal dependencies were updated in 5.3.4, most notably within the suite of @storybook packages. This means @storybook/api, @storybook/addons, @storybook/theming, @storybook/client-api, @storybook/components, and @storybook/core-events all transitioned from version 5.3.3 to 5.3.4. These updates likely incorporate bug fixes, performance enhancements, and compatibility improvements across the Storybook ecosystem. The release date of 5.3.4, January 16, 2020, indicates a quick follow-up to the previous version (January 14, 2020), suggesting a responsive approach to addressing potential issues or introducing minor enhancements. Developers should upgrade to 5.3.4 to ensure they are leveraging the latest improvements within the Storybook environment, promoting stability and potentially unlocking smoother integration with other Storybook addons and features. The file count and unpacked size remain the same across both versions, signaling that the fundamental structure of the addon hasn't undergone significant changes. By staying current with @storybook/addon-actions, developers get a reliable action logging experience in their Storybook setup.
All the vulnerabilities related to the version 5.3.4 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:
