@storybook/addon-viewport is a valuable tool for Storybook users, enabling them to easily simulate different viewport sizes, particularly useful for responsive design testing and ensuring consistent experiences across various devices. Comparing versions 5.3.5 and 5.3.4, the core functionality remains consistent, as they both serve the primary purpose of emulating mobile viewports within the Storybook environment.
While the description, license, repository details, fileCount, and unpackedSize remain identical between the two versions, subtle yet important differences exist in the dependencies and release timings. The key distinctions are in the versions of @storybook/api, @storybook/addons, @storybook/theming, @storybook/components, @storybook/core-events, @storybook/client-logger. Version 5.3.5 increments these dependencies to their respective 5.3.5 versions, while version 5.3.4 uses 5.3.4. These updates often incorporate bug fixes, performance improvements, or minor feature enhancements within the Storybook ecosystem. The release dates also differ, with version 5.3.5 being released later on January 16, 2020.
For developers, upgrading from 5.3.4 to 5.3.5 is generally recommended to benefit from the latest refinements and bug fixes in the core Storybook dependencies. If you're already using version 5.3.4 and haven't encountered any issues, the upgrade might not be critical for immediate stability but will ensure alignment with the broader Storybook environment. However, if you are facing issues related to Storybook's theming, API, or other core components, upgrading to 5.3.5 might resolve them due to the dependency updates.
All the vulnerabilities related to the version 5.3.5 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:
