@storybook/addon-viewport is a valuable tool for Storybook users, enabling developers to simulate various screen sizes and resolutions within their component library. This is particularly useful for ensuring responsive design and testing component behavior across different devices. The latest version, 5.3.13, builds upon the foundation of its predecessor, 5.3.12, offering subtle but important improvements.
While the core functionality remains consistent, a key difference lies in the updated dependencies for the stories themselves. Version 5.3.13 includes "@storybook/api": "5.3.13","@storybook/addons":"5.3.13","@storybook/theming":"5.3.13","@storybook/components":"5.3.13","@storybook/core-events":"5.3.13","@storybook/client-logger":"5.3.13", ensuring compatibility and leveraging the latest features offered by these core Storybook packages. Developers upgrading from 5.3.12 should see a smoother integration with the rest of the Storybook ecosystem. Also, the release date changed from 2020-02-04T23:22:35.744Z to 2020-02-12T03:49:49.681Z. Also, the dist tarball url is different.
Both versions share the same development dependencies and peer dependencies (react:"*"), signifying no major changes in the development workflow or required React version. Ultimately, the choice between 5.3.12 and 5.3.13 hinges on the developer's need for the latest Storybook API features and bug fixes included in the micro-version update. For those seeking the most up-to-date and integrated experience, version 5.3.13 is the recommended choice.
All the vulnerabilities related to the version 5.3.13 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:
