@storybook/addon-viewport version 5.3.10 is a minor update to the popular Storybook addon designed to help developers visualize and test their components across various screen sizes, particularly mobile devices. This addon empowers developers to simulate different viewport dimensions directly within the Storybook environment, streamlining the responsive design testing workflow. Comparing it to the previous version, 5.3.9, the core functionality remains the same, focusing on providing a convenient way to switch between predefined viewport sizes or define custom ones.
The key difference lies in the potential bug fixes and internal improvements. While a detailed changelog isn't provided here, the update from 5.3.9 to 5.3.10 likely addresses minor issues, optimizes performance, or enhances compatibility with other Storybook addons and core components. Developers upgrading should anticipate a more stable and refined experience. The file count reduced from 23 to 22, and a substantial difference in unpacked size 124531 to 28735 suggest optimizations.
For developers new to @storybook/addon-viewport, it offers a significant advantage in ensuring responsive designs. By integrating this addon, developers can proactively identify and resolve layout issues early in the development process, leading to a more consistent and user-friendly experience across different devices. The addon simplifies testing by eliminating the need to constantly resize browser windows or use external device emulators. It seamlessly integrates into the Storybook UI and provides a straightforward interface for managing viewport presets.
All the vulnerabilities related to the version 5.3.10 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:
