@storybook/addon-viewport offers developers a seamless way to simulate various screen sizes within their Storybook environment, crucial for responsive design testing and ensuring a consistent user experience across devices. Comparing versions 5.3.1 and 5.3.2, the core functionality remains consistent, focusing on viewport manipulation for mobile previews. A key distinction lies in the updated dependencies within version 5.3.2. Specifically, dependencies like @storybook/api, @storybook/addons, @storybook/theming, @storybook/components, @storybook/core-events, and @storybook/client-logger are bumped from version 5.3.1 to 5.3.2. This suggests that the newer version incorporates the latest improvements and bug fixes from those core Storybook packages, potentially addressing compatibility issues or enhancing performance. While the file count and unpacked size remain the same, the updated dependencies indicate a likely improvement in internal workings rather than significant feature additions visible to the average user. Developers are advised to upgrade to version 5.3.2 to benefit from the latest refinements in the broader Storybook ecosystem, ensuring stability and compatibility with other @storybook packages. Note the peer dependency on React; this package requires React to be installed in your project.
All the vulnerabilities related to the version 5.3.2 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:
