@storybook/addon-actions versions 5.3.2 and 5.3.3 offer developers a streamlined approach to logging actions within their Storybook environment. While both versions maintain the core functionality of the action logger, a closer look reveals subtle yet important distinctions. Most notably, the dependencies within the packages have been updated, specifically all @storybook/* dependencies have been updated from 5.3.2 to 5.3.3 to ensure compatibility and access to the latest features and bug fixes within the Storybook ecosystem. Developers leveraging version 5.3.3 benefit from these improvements, potentially leading to enhanced stability and performance.
Both versions bundle identical development dependencies, including @types/uuid and @types/lodash, essential for TypeScript support and improved developer experience. Furthermore, both packages share the same license, repository, file count, and unpacked size, indicating a consistent core structure and distribution method. The key differentiator lies within the updated @storybook/* dependency versions in 5.3.3, aligning it with the broader Storybook release cycle. Developers should upgrade to version 5.3.3 to stay current with the Storybook ecosystem, ensuring they have the latest improvements and bug fixes, ultimately contributing to a smoother and more productive development workflow. The release date also highlights that 5.3.3 released a day after 5.3.2.
All the vulnerabilities related to the version 5.3.3 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:
