@storybook/addon-actions versions 5.3.10 and 5.3.9 offer developers a tool to log actions performed within Storybook stories, providing valuable feedback during development and testing. This addon allows developers to track how users interact with components, making it easier to debug and ensure components behave as expected when triggered.
A key difference between the two versions lies in the internal structure and packaging. Version 5.3.10 significantly reduces the unpacked size of the package (52943 bytes) compared to version 5.3.9 (159779 bytes), this optimization, likely achieved through code splitting or removal of unnecessary files, translates to faster installation times and reduced disk space usage for developers.
Aside from the size optimization, both versions share the same core functionality and dependencies, including 'uuid' for unique ID generation, 'react' for the UI, 'polished' for styling utilities, and other essential Storybook packages like '@storybook/api', '@storybook/addons', '@storybook/theming', '@storybook/client-api', '@storybook/components' and '@storybook/core-events'. Dev dependencies remain the same. Therefore, upgrading from 5.3.9 to 5.3.10 would primarily benefit developers through improved installation efficiency without introducing breaking changes or new features. Version 5.3.10 was released a week later than version 5.3.9.
All the vulnerabilities related to the version 5.3.10 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:
