@storybook/addon-essentials, a powerful package designed to enhance your Storybook experience with a curated set of essential addons, saw a minor version update from 5.3.7 to 5.3.8. While both versions share the same core functionality and a consistent unpacked size, the key difference lies in the internal dependency versions.
Specifically, version 5.3.8 updates the dependencies @storybook/api, @storybook/addons, @storybook/node-logger, @storybook/addon-viewport and @storybook/addon-backgrounds to version 5.3.8 to match the addon version, ensuring compatibility and potentially incorporating bug fixes or performance improvements within those individual addons of Storybook. Developers upgrading should be aware of the potential subtle changes introduced by these dependency updates, though no breaking changes are expected in a minor release like this. If you are experiencing problems with storybook it is recommended to have all @storybook packages matching in version.
For developers using @storybook/addon-essentials, this package offers a convenient way to quickly integrate essential functionalities like viewport control, background customization, and logging directly into their Storybook setup. The peer dependencies of react, react-is and babel-loader remain unchanged. As both versions define these peer dependencies developers need to have them installed in their projects for the library to work correctly. Upgrading from 5.3.7 to 5.3.8 is highly recommended to benefit from the latest bug fixes and improvements within the core Storybook ecosystem reflected in the dependencies.
All the vulnerabilities related to the version 5.3.8 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:
