The @storybook/addon-viewport package, designed to empower Storybook users with the ability to effortlessly adjust viewport sizes for mobile responsiveness testing, saw a minor version update from 5.3.17 to 5.3.18. While the core functionality remains consistent, enabling developers to simulate various screen sizes directly within their Storybook environment, a few key distinctions exist between the two iterations. Foremost, the update involves internal dependency adjustments, primarily within the Storybook ecosystem itself. Specifically, dependencies like @storybook/api, @storybook/addons, @storybook/theming, @storybook/components, @storybook/core-events, and @storybook/client-logger have been bumped from version 5.3.17 to 5.3.18. These changes likely incorporate bug fixes, performance enhancements, or new features within those specific Storybook modules, indirectly benefiting the viewport addon.
Developers upgrading to version 5.3.18 can expect a smoother integration with the latest Storybook features and potentially improved stability due to the underlying dependency updates. The fileCount and unpackedSize remain identical suggesting there were no major changes to the code of the plugin itself besides the described dependency updates. This release emphasizes the continued maintenance and refinement of the Storybook ecosystem, ensuring a consistent and up-to-date experience for users leveraging the viewport addon for their responsive design workflows. The addon remains a valuable tool for front-end developers striving to create adaptable and user-friendly interfaces across a spectrum of devices.
All the vulnerabilities related to the version 5.3.18 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:
