The @storybook/addon-viewport package offers developers a seamless way to simulate various device viewports directly within their Storybook environment, aiding in responsive design testing and ensuring consistent UI across different screen sizes. Comparing versions 5.3.15 and 5.3.17, the core functionality remains consistent, focusing on providing a set of pre-defined viewport sizes and allowing custom configurations to mirror specific device dimensions.
The primary distinction between these versions lies in their internal dependencies, specifically the Storybook API, addons, theming, components, core events, and client logger which have been updated from version 5.3.15 to 5.3.17. This reflects general Storybook ecosystem updates and likely includes bug fixes, performance improvements, and minor feature enhancements within those core modules.
Developers upgrading from 5.3.15 to 5.3.17 can expect a smoother experience, leveraging the latest improvements in the supporting Storybook infrastructure. While the external API and usage of the viewport addon itself likely remain unchanged, developers benefit from a more robust and refined underlying platform. Both versions maintain peer dependency on React, ensuring compatibility with existing React-based Storybook setups. The util-deprecate type definition remains consistent. The MIT license guarantees the freedom to use and modify the addon according to individual project requirements.
All the vulnerabilities related to the version 5.3.17 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:
