Storybook addon viewport version 5.3.6 is a minor release over version 5.3.5, both serving as valuable tools for developers aiming to build responsive user interfaces within their Storybook environments. The core functionality remains consistent across both versions: enabling developers to effortlessly adjust the viewport size to simulate various mobile devices and screen dimensions. This allows for thorough testing and visualization of components and stories under different display conditions, crucial for ensuring a consistent and user-friendly experience across a range of devices.
While the description and file count remain identical, the key difference lies in the internal dependencies. Version 5.3.6 updates its reliance on other Storybook packages, specifically @storybook/api, @storybook/addons, @storybook/theming, @storybook/components, @storybook/core-events, and @storybook/client-logger, all bumped from version 5.3.5 to 5.3.6. This suggests bug fixes, performance improvements, or minor feature enhancements incorporated into these core Storybook modules. Developers upgrading to 5.3.6 will benefit from these underlying improvements without any significant changes to the viewport addon's API or usage. The release date difference indicates a quick follow-up addressing potential issues found in the prior version, suggesting a focus on stability and incremental refinement within the Storybook ecosystem, ultimately resulting in a more robust development experience.
All the vulnerabilities related to the version 5.3.6 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:
