@storybook/addon-actions version 5.3.14 introduces enhancements and bug fixes over the previous stable release, 5.3.13, making it a worthwhile upgrade for Storybook users. Both versions serve the same core purpose: providing an Action Logger addon for Storybook, allowing developers to easily display and inspect actions triggered within their stories.
The most noticeable change is the increase in the package size. Version 5.3.14 has a significantly larger unpacked size (68304 bytes) and file count (62) compared to version 5.3.13 (52943 bytes and 43 files respectively). This suggests the inclusion of new features, assets, or potentially more granular module splitting. While the specific nature of these additions isn't explicitly detailed in the metadata, developers might expect improved performance, new functionalities, or enhanced debugging capabilities related to action handling within their Storybook environment.
Both versions share identical dependency and devDependency listings, relying on key packages such as uuid, react, global, core-js, polished, prop-types, and other Storybook-related packages for their core functionalities. The core dependencies being the same means the core functionalities are not affected between versions and are probably related to internal improvements.
The release date difference (February 25, 2020, for 5.3.14 vs. February 12, 2020, for 5.3.13) indicates a roughly two-week gap between releases, implying that version 5.3.14 addresses issues or introduces features identified shortly after the release of 5.3.13, making it recommended to upgrade for developers using storybook.
All the vulnerabilities related to the version 5.3.14 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:
