@storybook/addon-viewport offers a simple yet powerful way to simulate different screen sizes within your Storybook environment, allowing developers to ensure their components are responsive and visually appealing across various devices. Version 5.3.4 introduces several key updates over its predecessor, version 5.3.3, primarily focusing on synchronization with the broader Storybook ecosystem. The most important change is the updated dependency versions of core Storybook packages. It upgrades dependencies like "@storybook/api", "@storybook/addons", "@storybook/theming", "@storybook/components", "@storybook/core-events", and "@storybook/client-logger" from version 5.3.3 to 5.3.4. These ensure compatibility and access to the latest features and bug fixes within the Storybook framework, leading to a more stable and efficient development experience. For developers, this means a smoother integration with other Storybook addons and the core Storybook platform. While the core functionality of the viewport addon remains consistent – providing a selection of preset device dimensions and the ability to define custom viewports – upgrading to version 5.3.4 is recommended to benefit from the synchronized updates and ensure long-term compatibility. The addon itself depends on react, and includes other utilities like core-js and prop-types.
All the vulnerabilities related to the version 5.3.4 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:
