@storybook/addon-viewport is a versatile Storybook addon designed to streamline responsive design testing and development. It empowers developers to effortlessly switch between various viewport sizes, mimicking the appearance of their components on different devices directly within the Storybook environment. This eliminates the need for constant resizing of the browser window or relying on external device emulators, accelerating the debugging and refinement of user interfaces for optimal viewing experiences across platforms.
The updates introduced between version 5.3.11 and 5.3.12 primarily involve synchronization with the core Storybook ecosystem. Specifically, dependencies like @storybook/api, @storybook/addons, @storybook/theming, @storybook/components, @storybook/core-events, and @storybook/client-logger have all been updated to version 5.3.12. While the changelog might not explicitly highlight feature additions or bug fixes for the viewport addon itself, aligning these core dependencies ensures compatibility, stability, and access to any underlying improvements or security patches present in the broader Storybook framework. For developers, staying current with the latest minor versions is crucial for leveraging the most robust and secure development environment, guaranteeing smooth integration and consistent behavior within their Storybook projects. This update reinforces the addon's reliability as a valuable tool in the responsive design workflow.
All the vulnerabilities related to the version 5.3.12 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:
