@storybook/addon-viewport is a valuable tool for Storybook users, allowing developers to simulate viewing their components on various devices by adjusting the viewport size. This addon is particularly helpful for responsive design testing, ensuring that components render correctly across different screen sizes, like smartphones and tablets, directly within the Storybook environment.
Comparing versions 5.3.8 and 5.3.9, the core functionality remains consistent, focusing on providing a seamless viewport adjustment experience. Both versions share the same set of dependencies, including essential packages like @storybook/api, @storybook/addons, @storybook/theming, and @storybook/components, all pegged to their respective Storybook versions to ensure compatibility. The peerDependencies specify React, indicating the addon's reliance on React projects. The file count and unpacked size are identical between the two.
The primary difference lies in the internal versioning of Storybook dependencies. Version 5.3.9 updates these internal dependencies (e.g., @storybook/api updated from 5.3.8 to 5.3.9), likely incorporating bug fixes, performance improvements, or new features within the broader Storybook ecosystem. For developers, upgrading from 5.3.8 to 5.3.9 provides access to the latest Storybook enhancements. Furthermore, the release date of 5.3.9 is later than 5.3.8 meaning that using the latest version will grant access to the most recent updates made to it. Although the core functionality concerning viewport manipulation most likely remains the same, staying up to date is generally a good practice.
All the vulnerabilities related to the version 5.3.9 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:
