@storybook/addon-actions version 5.3.8 represents a minor update to the Action Logger addon for Storybook, building upon the functionalities offered in version 5.3.7. While both versions provide developers with the ability to display action dispatches within the Storybook UI – crucial for interactive component development and debugging – there are subtle distinctions that might influence update decisions. The core functionality remains consistent: logging and visualizing actions triggered by component interactions, allowing developers to track data flow and ensure proper event handling within stories.
Key differences lie in the dependency updates and included development tooling. Version 5.3.8 introduces @types/webpack-env as a dev dependency, potentially improving the development experience for users working in webpack environments by offering better type definitions. Also, 5.3.8 appears to include core-js (^3.0.1) and polished (^3.3.1) as dependencies that were not listed in 5.3.7. The update also reflects a slight increase in unpacked size, which can point out to very small changes in the packages. For developers already using 5.3.7, the upgrade to 5.3.8 is likely a low-risk proposition. Given the dependency updates and the recency of the releases, upgrading ensures access to the latest improvements and potential bug fixes within the action logging capabilities. The small changes suggest a focus on refining the existing features and enhancing compatibility with common development workflows.
All the vulnerabilities related to the version 5.3.8 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:
