@storybook/addon-viewport is a valuable tool for Storybook users, enabling developers to easily simulate different screen sizes and resolutions, specifically mobile viewports, directly within their Storybook environment. This allows for efficient and comprehensive testing of UI components across various devices and scenarios, ensuring a responsive and consistent user experience.
Comparing version 5.3.20 with the previous stable version 5.3.19, the core functionality of the addon remains consistent, focusing on viewport manipulation. The key differences lie primarily in updated dependencies within the package. For instance, the "@storybook/api", "@storybook/addons", "@storybook/theming", "@storybook/components", "@storybook/core-events", and "@storybook/client-logger" dependencies appear to have been updated to version "5.3.20" to align with the new package version, from "5.3.19" in the previous version. This suggests internal updates within the Storybook ecosystem, potentially addressing bug fixes, performance improvements, or feature enhancements in these core modules. Although the changes might not be immediately visible to the end-user, these updates ensure compatibility and stability within the broader Storybook environment. The "unpackedSize" also changed from 30485 to 30484 bytes.
Developers using this addon can expect seamless integration with their existing Storybook setup. The peer dependency on "react": "*" indicates that the addon is compatible with a wide range of React versions. The consistent "fileCount" of 31 across both versions suggests minimal changes to the overall file structure of the addon. Upgrading from 5.3.19 to 5.3.20 should be straightforward, providing a smoother development experience.
All the vulnerabilities related to the version 5.3.20 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:
