@storybook/addon-viewport offers developers a streamlined way to simulate different device viewport sizes within their Storybook environment, aiding in responsive design testing and component visualization across various screen dimensions. Comparing versions 5.3.6 and 5.3.7, the primary divergence lies in the dependencies on other Storybook packages. In version 5.3.7, dependencies like @storybook/api, @storybook/addons, @storybook/theming, @storybook/components, @storybook/core-events, and @storybook/client-logger were updated to version 5.3.7, aligning them with the core Storybook ecosystem. Whereas, the previous stable version 5.3.6 uses the 5.3.6 versions of the same packages. While the core functionality related to viewport manipulation likely remains consistent between these versions, this dependency update suggests potential bug fixes, performance improvements, or feature enhancements within the underlying Storybook infrastructure. Developers should consider upgrading to version 5.3.7 to leverage these potential improvements and ensure compatibility with other Storybook addons that have been updated. Both versions maintain identical development dependencies, peer dependencies on React, licensing under MIT, repository location, file counts, unpacked size, and the same description indicating focus on mobile viewports, so the core impact remains the aligned ecosystem. For developers, this addon is particularly valuable for ensuring components look and behave as expected on a range of devices.
All the vulnerabilities related to the version 5.3.7 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:
