@storybook/addon-viewport is a valuable tool for Storybook users, enabling developers to responsively test and showcase components across various screen sizes, simulating different mobile devices and resolutions directly within the Storybook environment. Comparing versions 5.3.14 and 5.3.13 reveals subtle yet important distinctions for developers keen on maintaining stable and up-to-date Storybook setups. Primarily, the core functionality remains consistent, offering the ability to dynamically adjust the viewport within Storybook stories.
A key difference lies in the updated dependencies. Version 5.3.14 has newer versions of some of its internal storybook dependencies(@storybook/api, @storybook/addons, @storybook/theming, @storybook/components, @storybook/core-events, @storybook/client-logger), all upgraded to 5.3.14, aligning it with other Storybook packages and potentially incorporating bug fixes or minor improvements. This synchronization across the Storybook ecosystem is crucial for avoiding compatibility issues and leveraging the latest features. The increase in the fileCount and unpackedSize in version 5.3.14 suggests that the changes include additional files or updates to existing ones, potentially related to internal tooling, documentation or optimized assets. Developers should consider upgrading to version 5.3.14 to benefit from a more consistent and potentially more refined Storybook experience, ensuring smoother integration and leveraging the most current improvements within the Storybook framework.
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:
