@storybook/addon-viewport is a valuable tool for Storybook users, enabling them to simulate different screen sizes and resolutions, crucial for responsive design testing directly within the Storybook environment. Comparing versions 5.3.20 and 5.3.21, the core functionality remains consistent, focusing on providing a seamless way to preview stories across various viewport dimensions, mimicking mobile, tablet, and desktop experiences.
A key update in version 5.3.21 involves updates on internal dependencies, notably within the @storybook ecosystem. Specifically, @storybook/api, @storybook/addons, @storybook/theming, @storybook/components, @storybook/core-events, and @storybook/client-logger are all bumped from version 5.3.20 to 5.3.21. This indicates a synchronization effort within the Storybook project, likely including bug fixes, performance improvements, or feature enhancements across these core packages.
Developers using this addon benefit from a simplified workflow for responsive design. Instead of constantly resizing browser windows or employing external device emulators, the viewport addon allows instant switching between predefined or custom viewport configurations. The update to version 5.3.21 ensures compatibility and stability within the broader Storybook environment, leveraging the latest improvements made to the underlying Storybook infrastructure. While no groundbreaking feature additions are apparent between these specific versions, keeping up-to-date ensures developers are working with the most reliable and performant version of the tool.
All the vulnerabilities related to the version 5.3.21 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:
