@storybook/addon-actions version 5.1.9 is a minor release update to the popular Storybook addon, a crucial tool for developers creating UI components in isolation. Primarily designed for logging actions that occur within your components during Storybook interactions, it provides valuable feedback for testing and debugging. Comparing it to the previous stable version, 5.1.8, the core functionality remains consistent, focusing on capturing and displaying event data triggered by user interaction with Storybook stories.
The key area of change lies within the internal dependencies. While developer-facing APIs are highly likely unchanged, 5.1.9 updates its dependencies to newer versions of @storybook/api, @storybook/addons, @storybook/theming, @storybook/components and @storybook/core-events all to version 5.1.9, reflecting a synchronization with other Storybook packages. This indicates a focus on internal consistency and bug fixes across the Storybook ecosystem. Developers adopting 5.1.9 can expect improved stability and better compatibility with the rest of the Storybook environment. The devDependencies remain untouched, suggesting that the update is mainly a maintenance release related to the core Storybook framework rather than new features or changes to how developers interact with the addon. If you're already using @storybook/addon-actions and Storybook, upgrading to 5.1.9 is recommended to leverage bug fixes, dependency updates, and ensure compatibility across your Storybook environment. Consider checking the Storybook changelog for complete context to fully grasp the updates included in the ecosystem.
All the vulnerabilities related to the version 5.1.9 of the package
node-fetch forwards secure headers to untrusted sites
node-fetch forwards secure headers such as authorization, www-authenticate, cookie, & cookie2 when redirecting to a untrusted site.
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.
Prototype Pollution in highlight.js
Affected versions of this package are vulnerable to Prototype Pollution. A malicious HTML code block can be crafted that will result in prototype pollution of the base object's prototype during highlighting. If you allow users to insert custom HTML code blocks into your page/app via parsing Markdown code blocks (or similar) and do not filter the language names the user can provide you may be vulnerable.
The pollution should just be harmless data but this can cause problems for applications not expecting these properties to exist and can result in strange behavior or application crashes, i.e. a potential DOS vector.
If your website or application does not render user provided data it should be unaffected.
Versions 9.18.2 and 10.1.2 and newer include fixes for this vulnerability. If you are using version 7 or 8 you are encouraged to upgrade to a newer release.
Manually patch your library to create null objects for both languages and aliases:
const HLJS = function(hljs) {
// ...
var languages = Object.create(null);
var aliases = Object.create(null);
Filter the language names that users are allowed to inject into your HTML to guarantee they are valid.
If you have any questions or comments about this advisory:
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: