Storybook Dev Server WebSocket Hijacking Risk

Summary

If you're using an older version of Storybook's dev server, a hacker could potentially take control of your local development environment by sending malicious messages to your computer. This is a risk if you're sharing your dev server publicly, but it's not a concern if it's only accessible from your local machine. Update to the latest version of Storybook to fix the issue.

What to do

Update GitHub Actions storybook to version 8.6.17.
Update GitHub Actions storybook to version 9.1.19.
Update GitHub Actions storybook to version 10.2.10.

Affected software

Vendor	Product	Affected versions	Fix available
GitHub Actions	storybook	> 8.1.0 , <= 8.6.17	8.6.17
GitHub Actions	storybook	> 8.7.0-alpha.0 , <= 9.1.19	9.1.19
GitHub Actions	storybook	> 10.0.0-beta.0 , <= 10.2.10	10.2.10
storybook	storybook	<= 7.6.23	–
storybook	storybook	> 8.1.0 , <= 8.6.17	–
storybook	storybook	> 9.0.0 , <= 9.1.19	–
storybook	storybook	> 10.0.0 , <= 10.2.10	–

Original title

Storybook is a frontend workshop for building user interface components and pages in isolation. Prior to versions 7.6.23, 8.6.17, 9.1.19, and 10.2.10, the WebSocket functionality in Storybook's dev...

Original description

Storybook is a frontend workshop for building user interface components and pages in isolation. Prior to versions 7.6.23, 8.6.17, 9.1.19, and 10.2.10, the WebSocket functionality in Storybook's dev server, used to create and update stories, is vulnerable to WebSocket hijacking. This vulnerability only affects the Storybook dev server; production builds are not impacted. Exploitation requires a developer to visit a malicious website while their local Storybook dev server is running. Because the WebSocket connection does not validate the origin of incoming connections, a malicious site can silently send WebSocket messages to the local instance without any further user interaction. If the Storybook dev server is intentionally exposed publicly (e.g. for design reviews or stakeholder demos) the risk is higher, as no malicious site visit is required. Any unauthenticated attacker can send WebSocket messages to it directly. The vulnerability affects the WebSocket message handlers for creating and saving stories. Both are vulnerable to injection via unsanitized input in the componentFilePath field, which can be exploited to achieve persistent XSS or Remote Code Execution (RCE). Versions 7.6.23, 8.6.17, 9.1.19, and 10.2.10 contain a fix for the issue.

nvd CVSS4.0 8.9

Vulnerability type

CWE-74 Injection

CWE-79 Cross-site Scripting (XSS)

CWE-1385